Managing Permissions and Access Control
Permissions can be set at different levels in the system (the company, project, or shell level).
The permission settings can be done in these functional nodes:
- Access Control
- Company User
- User Administration, Groups sub-node
- Standards & Libraries, Permissions sub-node
Note: To assign permissions to the Oracle Primavera Cloud functional node (Integrations node, Primavera Cloud sub-node), use the Access Control node.
A user can be granted permissions individually or can inherit them from the groups to which the user belongs.
If a user is in more than one group, the highest level of permissions granted in any group for a module will prevail.
Users can be granted individual permissions in addition to group permissions. If the user-level and group-level permissions are different for a module, the highest level will be granted to the user.
Note: If you grant permissions to shell-level (User mode) features from the company-level, the new permission settings will take effect on future projects and shells the user is assigned to, but not on current projects and shells. To grant permissions to a user for a current project, be sure to change the permissions from the shell-level user record.
Permissions in a shell template from which the project or shell is created override the company-level permissions.
In This Section
Permissions Tab versus Access Control
Edit User or Group Permissions Using Access Control
Create or Edit a Permission Template
Generate and Print an Access Information Report
Last Published Tuesday, April 15, 2025