Skip to main content
Orion has three tenant-level roles you can assign: Admin, Analyst, and Viewer. They control baseline permissions. Admins invite users, assign roles, and manage group membership from Admin Settings → Users. Users and Groups are managed from the same page.

Accessing User Management

User Management is available to tenant Admins and to Group Admins. To access it:
  1. Click Admin Settings in the left-hand navigation menu
  2. Select Users in the Admin Settings sidebar
The Manage Users page has two tabs: Users (everyone in the tenant) and Groups (groups of users that share access to projects, data, and knowledge).
Manage Users page in Admin Settings on the Users tab, with a search box, Add User, and a table of five users with Role, Project Access, and Groups columns

Tenant users and their access

Use the search box to filter by name, email, role, or project. The Role and Project Access columns on each row are controls: both change what that user can reach.

Inviting New Users

To invite a new team member to your Orion tenant:
  1. Navigate to Admin Settings → Users
  2. From the Users tab, click Add User
  3. Enter the new user’s email address
  4. Choose the appropriate role
  5. For an Analyst or Viewer, optionally pick projects in the Project access step and groups in the Group assignment step
  6. Click Send invite
An Admin invite skips the Project access and Group assignment steps, because a tenant Admin already has full-tenant scope. The Group assignment step appears only when the tenant has groups. The new user will receive an email with instructions to complete their account setup. See User Onboarding & Invitations for more details. Group Admins can also invite. Their invitees always get the Viewer tenant role, must join at least one group the Group Admin administers, and can only be added to projects the Group Admin administers.
To onboard a new user directly into a group, invite them from inside that group instead. Open the group, click Add member, then Invite by email and the invitee is automatically added to the group with the role you pick on first login. See Groups for details.

Tenant Roles

Every user has a tenant role that defines their baseline permissions across the entire tenant.

Admin

Full control of the tenant. Can invite users, create and manage groups, connect data sources, and assign users to projects.

Analyst

Can do just about anything within a project: chat, run analyses, and share projects. Cannot add existing users to other projects directly.

Viewer

Read-only access to approved projects and content. Cannot run analyses or make changes.
Carefully consider permission levels when inviting users, especially for administrative roles.

Tenant roles vs. group roles

If you use Groups, each user also has a group role in every group they belong to (Group Admin, Group Analyst, or Group Viewer). Group roles are independent of tenant roles and only apply inside that group, so a tenant Viewer can still be a Group Admin in a group they manage. For a side-by-side comparison of all six roles, see Groups → Roles at a Glance.

Changing a User’s Tenant Role

Pick the new role in the Role select on the user’s row, then confirm. Each role is described under Tenant Roles. Admin is the consequential direction: an Admin reaches every project, every group, and tenant-wide settings. Only Tenant Admins can change a role. A Group Admin sees a read-only badge in that column instead. Nobody changes their own role, Tenant Admins included: ask another Tenant Admin. The column can also read Visitor, a role SSO assigns and nobody assigns here. You can move a Visitor to Admin, Analyst, or Viewer. The select does not offer Visitor, so the move is one way. See Portal visitor domains for what a Visitor can reach.

Project Access and Group Membership

Click the count in the Project Access column to open Manage Projects. Check a project to grant direct access, clear one to revoke it, then click Save Changes. Only Tenant Admins can save here: the save fails for a Group Admin. This grants and revokes direct access only. Clearing every box still leaves the user the projects their groups carry, so change their group membership for those. See How users get access to a project. The Groups column names the groups a user belongs to, and does not set their role in any of them. Group roles are changed on the group’s own Members tab.

Deactivating a User

Deactivation removes a user’s access and keeps their history. Open the three-dot menu on the user’s row and select Set as Inactive. Set as Active restores access. To see Orion as another user without changing their access, Sudo as a user instead.

Best Practices

Follow the principle of least privilege: grant users the minimum permissions they need to do their job. For tenants using Groups, prefer group membership over direct project access: it’s easier to audit and easier to revoke when someone’s role changes.