To access an SDL Studio GroupShare resource, a user needs permissions.
When a user tries to access a resource, for example to update a TM, GroupShare compares the user's permissions to the permissions needed to do the action. If the user does not have sufficient permissions, the system does not perform the action.
A user's permissions for a resource are defined by the user's role in the organization which holds the resource:
A role is a group of permissions. Using roles, you give users a number of permissions at the same time. For example you might create a role administrator that grants all permissions.
Each organization holds a table of users and their roles in that organization.
A user can have one or more roles in an organization. If a user has a role, they have the permissions granted by the role.
A user can, and usually does, have different roles, and therefore different permissions, in different organizations.
The list of users and roles in an organization can give additional roles to a user, but cannot remove a role from a user.
The effective permissions that a user has in an organization consists of the sum of those granted by the user's roles in all the containing organizations.
Organization user role permission
Topic: Published: 27-Jun-2012