The user management page allows you to view and manage users in the system, making it easy to find, review, and take action on individual user accounts.
Accessing the User List
To access the User List:
Click the Settings gear in the top-right corner of the header
Select User management
This opens the User List, where you can view and manage all users in your organization.
.png)
Understanding the User List
When you open the User List, you’ll see a table displaying all users in your organization along with key information:
Name – The full name of each user.
Email – The email each user used to sign up to Prevu3D.
Administrative role (if applicable)
Displays whether the user has an administrative role.
Possible values:
Regular user (no administrative access)
Super Admin
A custom administrative role (Enterprise)
Administrative roles control access to settings and governance areas (users, permissions, SSO, subscription, etc.).
For a detailed explanation of administrative roles and how they differ from regular users, see Roles & Permissions.
Group membership – Shows which groups the user belongs to.
Groups are used to assign access and roles at scale. If a user is part of multiple groups, their permissions may combine based on those assignments.
Content access – Displays the content the user has access to (for example divisions, sites, twins, plans, or data).
Content access determines:
Where the user can go
What role applies in each context
If a user has multiple access points (for example via both direct assignment and groups), permissions are combined.
Regular user vs Administrative role
When inviting a user, you must decide whether they need access to settings and governance features, or only to content.
These are two separate concepts.
Regular user (most common)
A Regular user:
Does not have access to organization or division settings
Cannot manage users, roles, permissions, SSO, subscription, or billing
Regular users are assigned:
Division access
Content access
In most organizations, the majority of users should remain Regular users.
Administrative roles
An Administrative role grants access to platform settings and governance areas.
Depending on the role, an administrative user may be able to:
Manage users and groups
Configure roles and permissions
Configure SSO and integrations
Manage subscription and invoices
Create or manage divisions
Important:
A user can have only one administrative role
Administrative roles can be scoped to:
The entire organization (all divisions)
Specific divisions only
Administrative roles primarily control settings access, not content permissions by themselves.
However, there is one exception:
Super Admin has full access across the organization, including all divisions and all content. Super Admins automatically have full visibility and control over content.
For all other administrative roles, content visibility depends on the Nested Context configuration defined in the permission matrix.
An administrative role may:
Have a defined content role (for example Manager, Editor, Viewer) in the Nested Context
→ The user will see and interact with content accordingly.Be set to No Access in the Nested Context
→ The user will not see any content, even if they can manage settings.
This allows you to create roles such as:
Billing Manager → Can access subscription and invoices, but sees no content.
Division Admin with Viewer content role → Can manage users in a division but only view its content.
Division Admin with Manager content role → Can manage users and fully manage content within assigned divisions.
Invite a User
Go to Settings → User management
Click Invite user
Enter the email address
Configure:
Administrative role (if needed)
Group membership
Content access and role
Send invite
Most users should remain Regular users and receive access through groups.
Edit a User
Open Settings → User management
Select the user
Update:
Administrative role
Group membership
Content access
Save
Remove a User
Open Settings → User management
Click Remove user
The user immediately loses access to the organization and its content.
If you remove a user from a group only, they may still retain access if they have other assignments.