User access and permissions

There are various settings that determine which features a user can access and which actions they can perform, including:

  • Module assignment - the modules assigned to a user grant certain permissions and give access to various portal pages and entities.

  • User group membership - each member of a user group inherits the permissions defined in the group's policies.

  • User group policies - user group policies determine who has access to what, and which actions they can perform.

  • Project roles - grant access to (and determine permissions for) projects, jobs, stages. Similarly, user roles grant access and determine permissions for asset collections and content collections.

For example, let's say you want the Demo.Photographer user to only see their assigned tasks on the Tasks page. To achieve this, the Demo.Photographer:

  • Is assigned the Project module.

  • Is a member of the W.Photographers user group, which assigns Read permission for Portal.Page definitions only.

  • Is a member of the Everyone user group, which assigns the minimum permissions required by a user in Content Hub; and the M.Builtin.Project.Everyone user group, which assigns Read permission for pages related to projects, tasks, and jobs.

  • Has no project roles.

The following image illustrates the various permission layers.

Hierarchy of permissions

Do you have some feedback for us?

If you have suggestions for improving this article,