The CELUM Content permission system

CELUM Content's permission system is based on three simple principles:

  1. Permissions control both global access to specific functions and local access to specific collections/assets for any given user or user group. Local permissions are defined in "Roles" which are assigned to a specific user or group on a specific collection.

    A concrete example for local and global permissions

  2. There are two kinds of collections in CELUM Content with regard to permissions: Permission-defining collections define local permissions for themselves and also for all assets within. Non-permission-defining collections only define local permissions for themselves. Assets in non-permission-defining collections are unaffected by their parent collection's permissions.

    A concrete example for this principle

  3. Permissions are additive, which means that a permission granted to a user on a specific function or object cannot be withdrawn on the same object or function with a different permission set.

    Concrete examples for additive permissions

These three principles for permissions allow CELUM Content to represent your organization's real-world employee hierarchy and privileges in a highly granular and efficient way.

General user types

In the CELUM Content help, users with different permission levels are simplified in three types who have access to different functions:

Which global permissions are there?

Which local role-based permissions are there?

 


 

Want to restrict permissions yourself? The Administrator Guide in the Customer Knowledge Base contains instructions.