Access control for personalization objects

If we work with Personalization, we have a role assigned to you. This role defines the tasks we can do. We might be able to personalize folders and files, or we might have read-only access. We might also have the highest level of control, the administrative role that gives you permission to determine who has access to certain objects.

For administrative control, we can set access control for an individual object, or we can set access control for a folder. If we set access control for a folder, all of the folder's contents have the same access settings.

User roles

User roles that apply to personalization include user, editor, manager, and administrator.

The following user roles do not apply to personalization: privileged user, delegator, and security administrator.

User

The User has read-only access to Personalization objects. Users can see the resource, but cannot modify or contribute content of their own.

Editor

The Editor can view and add folders or documents to the current resource. Editors can also modify the properties and content of existing documents and files. Editors cannot move files.

Manager

The Manager has all the privileges of Editors. The Manager can also modify the properties and content of all objects, delete folders and objects underneath the current resource, override document locks, and move objects.

Administrator

The Administrator can do everything the user, editor, or manager role can do. The Administrator can also assign access to Personalization objects.

Examples

Here are some example role assignments:

• Someone who is not on the project can have a User role.

• Editors and writers can have an Editor role.

• Team leads and managers can have a Manager role.

• A project manager or manager can have an Administrator role.

Parent Personalization