Introduction to the Evo admin role

An Evo instance is the highest-level deployment of the Evo platform that is owned by an organisation and deployed to a regional hub. Your organisation may have multiple Evo instances, perhaps deployed to different regional hubs. Data in an instance is organised into workspaces where access is controlled by assigning users and granting them different permission levels.

It is important to understand the following characteristics of an Evo instance:

  • The pool of users who belong to an Evo instance is not shared with other instances. Although a Bentley account may provide someone with access to multiple Evo instances, management of their access to each instance is separate from the management of the other instances.
  • Workspaces are unique to an instance; they cannot be shared across instances.

This topic introduces the Seequent Evo instance admin role and provides links to more information to help you get started. It is divided into:

Evo user roles and workspace permissions

Evo instance user roles and workspace permissions control what data each user on an instance has access to.

User roles

User roles determine what a specific user can do in the instance. Evo instances have two possible user roles:

  • Users have limited access to the instance, based on what workspaces they have permissions for.
  • Admins have full access to the instance.

An instance user can:

  • See workspaces they have been assigned to
  • Create new workspaces
  • Assign other users who belong to the instance to a workspace with permissions that are equal to or lower than their own, if they have a permission level that allows them to do so

An instance admin has full access to the instance. They can:

  • Add new users to the instance
  • Revoke access to the instance for existing users
  • See all workspaces in the instance, even those to which they have not been assigned

Note that some workspace actions can only be carried out if the admin has the workspace permissions to do so.

Workspace permissions

In workspaces, there are three different permission levels that determine how you work with data in the workspace:

  • Viewers can view and search all data in the workspace.
  • Editors can edit data and add data to the workspace. An editor can also share the workspace by adding users, although they cannot give users permissions higher than their own.
  • Owners can edit data and add data to the workspace, and can share the workspace. Owners can also delete the workspace. By default, the user who creates a workspace is assigned as an owner. A workspace can have multiple owners, if required.

If an Evo user has none of these permissions for a workspace, that workspace is not visible to them. Only Evo admins can see all the workspaces in an instance.

See the Workspace permissions topic for more information on what is possible at the different permission levels.

Differences in workspace management for admins and users

Whereas Evo users can only see workspaces they have permissions for, admins can:

  • See all workspaces in the instance
  • Add users to any workspace
  • Change user permissions for any workspace
  • Remove users from any workspace

Evo admins must be assigned to a workspace with the correct permissions in order to:

  • View data in the workspace
  • Change workspace settings
  • Remove the workspace
  • Restore the workspace from the recycle bin

See the Workspaces help for more information on these tasks.

Adding and removing users

Only instance admins can add new users to the instance. When an instance user wishes to add someone who is not a member of the instance to a workspace, they will need to contact an admin to do this for them. Users can find out who the admins are by clicking on Users in the sidebar.

See the separate Managing instance users topic for information on adding new users to an instance and removing existing users.