Scope Roles

Each default user group is assigned a security role in PowerWeb, where the role is a named set of permissions. This assignment can be different based on its project type or document type, thus allowing the security to be very flexible based on each user's role and responsibilities.

Note:

Do not assign users to multiple default user groups, because security roles can conflict. For example, Reviewers and Approvers roles cannot Edit properties. Therefore, Project Owners, Document Controllers, and Contributors should not be added to Reviewers or Approvers groups.

This security role is then assigned permissions within a scope. A scope is used to control the availability of commands, views, and documents in PowerWeb. The configuration of each scope is hard-set, and cannot be modified by a Tenant Administrator. Certain permissions may be allowed by the security role to enable functionality, but they may not be accessible by the scope.

Important!

Do not delete or rename the Archive, Documentation, Masters, or Projects root folders. They are used in scope roles.

Concept Information

Scopes

Vault Structure

Manage User Groups

Concept Information

Global Security Role

Master Scope Roles

Project Scope Roles

Documentation Scope Roles

Tags Scope Roles

Archive Scope Roles

Configure Role-Based Security

Concept Information

Select a Scope

 

Accruent logo in white text.

© Copyright Accruent 2024Privacy PolicyTerms of UseLegal