Designer 10.15 | Centrasite Eclipse UI Help | Concepts | Security | Users, Groups and Roles in CentraSite
 
Users, Groups and Roles in CentraSite
A user to whom access can be granted or denied in CentraSite is a user who is known to an external authentication system (such as an operating system or Active Directory Server) and is mapped to a registry object of the User type. Registry objects of the User type are inactive until they are associated with an external user. Only active users can log on to CentraSite. For creating users and associating them to external users, use the CentraSite Control (Web interface). The Registry Explorer View of the CentraSite Eclipse GUI enable you to access the User objects and see whether a user is active or inactive.
A role defines a set of permissions. Each user is assigned at least one role. When a user is assigned to a role, he/she receives all the permissions defined for the role. CentraSite distinguishes between system-level roles and organization-level roles. Whereas system-level roles apply across all organizations, organization-level roles are effective for exactly one organization. For both types, CentraSite provides predefined roles. You can also create your own system-level and organization-level roles to suit your organizational requirements.
The following roles are examples of predefined system-level roles in CentraSite:
*CentraSite Administrator: The main administration role which provides access to the complete set of functions that is available in CentraSite.
*Guest: The default role for unauthenticated users. Users with this role are permitted to search and browse the assets stored in the CentraSite registry.
*Asset Type Administrator: A user with this role is permitted to create and manipulate object types and taxonomies.
The following roles are examples of predefined organization-level roles in CentraSite:
*Asset Provider: A user with this role can create and manage registry objects. Depending on the permission's scope, the user can either create and manage registry objects for their organization only or for all organizations defined in CentraSite.
*Asset Consumer: A user with this role can read registry objects. The user cannot create new registry objects. Depending on the permission's scope, the user can either read registry objects of their organization only or of all organizations defined in CentraSite.
*Document Administrator: A user with this role is responsible for managing an organization's Supporting Documents Library. The user can view, add, edit and delete documents.
A group defines a set of users with identical roles and permissions. CentraSite provides predefined groups. You can also create your own groups to suit your organizational requirements.
The functions for user, group and role management are available in the CentraSite Control (Web interface). For detailed information, refer to the documentation which comes with the CentraSite Control.