PROJECT SECURITY
Use Restricted User's Permissions when a project needs access to be assigned explicitly.
OpenGround user and access guides Current article: Manage Confidential Projects
| Get ready | Bentley account prerequisites |
| Create users | Create and manage users |
| Access overview | OpenGround access: quick overview |
| Understand access | Access Levels & Roles |
| Assign access | System administrator · System-level access · Project access |
| Protect projects | Confidential projects |
Some projects need tighter access controls than the organization's default project assignments. During project creation, set Restricted User's Permissions to prevent default user permissions from granting access automatically.
With this setting, users need to be granted access to the project explicitly. Review the project's access list after creation and add only the users and groups that should have access.
Important exception: The source guidance says Restricted User's Permissions does not block System Administrators, users in System Access Groups with the View or Link User roles, or the project creator. Those users may still view or access the project. Confirm these exceptions against your current OpenGround configuration before relying on the restriction as a confidentiality boundary.
For project assignment workflows, see Manage Project Access. For system-level role precedence, review Access Levels & Roles.