I should have looked here. It is a known issue:

https://gateway.sdl.com/apex/communityknowledge?articleName=CUs-GroupShare-2017-SR1

• Resolved an issue where a user without delete termbase permission was able to remove the termbase from the list of termbases

Apparently it was resolved with the latest GroupShare CU10 just released.

Daniel

Hi Daniel

thanks for your reference. OK if it was resolved for Groupshare 2017, but it may still be an issue in Groupshare 2015 at that point.

Bruno

Bruno Ciola

Can you confirm what version you are running as this should have been resolved last year in Cumulative Update 8 - Build 32756 (released 3rd of September 2018).

Thanks

Bruno Ciola

Can you confirm what version you are running as this should have been resolved last year in Cumulative Update 8 - Build 32756 (released 3rd of September 2018).

Thanks

Bruno Ciola

Apologies... that was a silly question, I see you are using Studio 2019 and MT 2015.  The issue should not be there in the current version of GroupShare.

Is there a reason why you are still using GroupShare 2015?  I don't know whether we will resolve these things in the older versions, Phillip Maieski might be able to confirm.

Hi Paul

we decided to split up the Studio 2019 and Groupshare migration to avoid too many "issues".

BTW on our test server with Groupshare 2017 CU9 it is also possibile to delete termbases.

And I cannot see the resolved issue in CU10, Daniel García Magariños:

• "Resolved an issue where a user without delete termbase permission was able to remove the termbase from the list of termbases"

Here the TB is not removed from the list but deleted completely from the server.

Regards,

Bruno

Hi, Bruno, you are right. I mixed the issue. I have reported the problem to SDL support, who confirmed the issue and got a CRQ number. I guess they will do the same when you report it.