Under Community Review

enhance permission management

If a user has read/write access at the language level, that user can delete the language object before it's added to a publication. My suggestion is to enhance the administrative abilities to better dictate the user role allowed to delete objects.

  • We had a situation where a user had three files checked out via Oxygen Author. She has rights to edit, so this was fine. Somehow she ended up deleting all three language objects. I asked her what happened and she said she did nothing unusual, but her Oxygen Author instance crashed that morning while she had files checked out. I checked with SDL support and they said the crash had nothing to do with the files deleting. Whether the issue is files deleting via technical issue or files deleting due to user error, this was a serious issue as it resulted in losing the history for three files. We were able to recover recent copies through the local storage, but they weren't the latest. We have users who are scientists and edit files, but may not understand the implications of actions in the CCMS. 

  • Could you provide me more details on your use case? Is this a common situation at your practice?