OpenGround Access: Quick Overview


GETTING STARTED WITH ACCESS

OpenGround access: quick overview

The essentials for understanding licenses, roles, and project access before you add people to your environment.

OpenGround user and access guides 

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 Manage confidential projects

Access has three separate parts: a Bentley account and license entitlement, an OpenGround user account, and permissions that determine what the user can do. A Bentley Account Administrator manages identity and entitlements; an OpenGround administrator manages users and access inside the environment. One person may hold both responsibilities, but they are not the same permission.

Common license and role alignment

For most organizations, the following is a useful starting point. License-to-role assignments and role configuration can vary, so confirm the mapping with your organization's licensing and OpenGround administrators.

License Common role alignment Access note
Base User license Edit User role Commonly aligns with users who need to enter or update project data.
Advanced User license Project Manager User role Project creation access may be included or assigned separately; verify the user's Create Project permission.

A license does not by itself grant access to a specific project. The user's role and project membership must also be configured.

Choose the right access scope

Check broad roles carefully: A system-level role can grant permissions that are more permissive than a project's group. Avoid overlapping or unnecessarily broad roles when configuring access.

What happens when you add a user?

Default security groups selected during user creation apply to projects created after the user is added. They do not automatically grant access to existing projects. Add users to existing projects through User Access or Project Access.

Projects configured with Restricted User's Permissions require explicit access assignments. System Administrators, some system-level roles, and the project creator may still have access; confirm the current exceptions for your environment.

Continue to the task guide

To create an account, open Create and manage users. For detailed access definitions and procedures, use Access Levels & Roles, Assign System Level Access, and Manage Project Access.