ACRs, Roles and Scopes

Each user can be given one or more Access Control Rights (ACRs). Each ACR consists of two parts:

• A Role, which defines what operations a user can carry out on which elements; for example, create, modify and delete all types of Piping elements.

• A Scope, which defines the part of the design to which the Role applies; for example, a particular Site (in Model) or Registry (in Draft), or a specified volume within the 3D model.

  Roles and Scopes must be created before the user can create ACRs. They are both defined within a project, but Roles are likely to be company-wide and used for all projects, and so they are defined in very general terms, whereas Scopes are project-specific.