Roles and Role-Based Permissions
A role is a set of role-based permissions. Role-based permissions enable users to access areas of the CentraSite Control user interface and to create and manage (view, edit, and delete) certain types of registry and repository objects. You can assign roles to a user or a group; the user or users in the group receive the permissions specified in the role.
By default, all CentraSite users, including guests, have permission to use the Asset Catalog area of the CentraSite Control user interface, and all users except guests have permission to provide and consume assets within their own organization. To use the other parts of the user interface or have access to other objects, a user must belong to a role that includes the appropriate permission.
Role-based permissions are at two levels:
System-wide permissions grant access to objects that are available to all organizations, such as taxonomies and asset types. Additionally, some system-wide permissions grant access to all objects of given type in any organization in the registry/repository. System-wide permissions are generally given only to a small group of high-level administrators.
Organization-specific permissions grant access to all objects of a certain type within one organization. Permissions that enable access to assets, policies, and lifecycle models are organization-specific.
CentraSite comes with predefined roles for each level of permissions. If necessary, you can create custom roles.
System-level roles contain permissions that enable users to work with system-wide objects. Some of these roles also enable users to manage (view, edit, or delete) all instances of a given object type in any organization in the
CentraSite registry/repository.
Organization-wide roles contain permissions for working with organization-specific objects.
CentraSite maintains a set of organization-level roles for each organization in the registry/repository.
