4

When you create a new publication, Tridion applies some sensible default rights for the built in groups like Editor and Chief Editor. We built our security model on top of these default groups, so when we create new publications, the only configuration we have to do with regards to authorization is to alter the group scope to include the new publications.

The exception to this seems to be rights for optional modules like Translation Manager. It seems like we always have to manually add this right to the required groups for each new publication, which is is bit of a pain.

Looking at the docs, this does not seem possible, but I thought I would check anyway: Is there some way to also define defaults for these additional rights which come from optional modules so we don't have to keep doing this? We are using SDL Web Cloud (8.6)

enter image description here

5

Is there some way to also define defaults for these additional rights which come from optional modules so we don't have to keep doing this?

Not that I know of.

It seems like we always have to manually add this right to the required groups for each new publication, which is is bit of a pain.

You could utilize the Event System system to set these right. The way to do it is through the Repository.AccessControlList property.

  • 1
    Yep, I agree with you probably having to do this through the Events System. Rights for the additional modules (Translation, etc.) tends to be done through App Data on the Publication, rather than the normal Publication properties though, so you'll have to do some XML creation/manipulation. – Jonathan Williams Dec 12 '18 at 11:00
  • Good point on the App Data, totally slipped my mind (I remember schema fields' translatable options also being set in App Data) – Atila Sos Dec 12 '18 at 11:12
  • Technically speaking, the default Publication rights are “configured” in a DB table (DEFAULT_REPOSITORY_RIGHTS), but there is no public API to change those. So, +1 for Event System. – Rick Pannekoek Dec 13 '18 at 7:18
1

In the past, (where the client had a tool to create new publications with specific blueprint setups depending on selected options) we added a simple extension to select 'default' permissions (that would ideally have been inherited) and then options to override them (if you were a member of a specific user group) - all interacting through the Core Service obviously.

You'll not be far wrong looking at the Powershell modules as a starter.

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.