Roles are an abstract grouping of users and Content, and provide a way to provision Content across Domains. For example, an administrator may many want all “Executive” users to get the same set of pages, regardless of what Domain they belong to. This is achieved by:
Multiple Roles can be assigned to users, either directly at the User level, or inherited through a user’s Domain. When a user logs into the system, they do not assume a specific role. The system determines all of the Content assigned to all of his or her Roles, and presents an aggregate view of all of that Content.
To create a new Role, follow the steps below:
Role names are required to be unique.
To delete an existing role, follow the steps below:
Deleting a Role will remove it from the system, but all associated users and content will remain. Their association to the Role will be lost.
To provision Content to a Role, follow the steps below:
To grant permission for Users in a Role to manage other Users:
There are 2 special domains that can be selected for Partial Admin provisioning: <AllDomains> and <MyDomain>
To add, edit, or delete Users from a Role, follow the steps below:
From the Role perspective, you can only add associations to Users that are already in the system. (To add a new user to the System you would need to first switch to the Manage By: User, or Manage By: Domain perspective.)
To add Users to a Role, follow the steps below:
Adding a User to a Role is equivalent to adding a Role to a User.
Although you can’t “Add” a new User to the system while in the Role perspective, you can “Edit” existing Users because they already belong to a specific Domain.
To edit a User, follow the steps below:
To remove a User from a Role, follow the steps below:
From the Role perspective, in the above example you are only removing the association to a User who is already in the system. (To completely remove a User from the system, you would need to first switch to the Manage By: User or Manage By: Domain perspective.)