Skip to main content
Groups let you organize users into cohorts that share access to the same set of projects, data sources, Context pages, and Integrations. Use them to model teams, departments, end customers, or any other grouping that maps to a set of people who should see the same resources.

When to use Groups

Departments

Sales, Marketing, Finance, and Operations each get their own group with the projects, data sources, and Context pages relevant to their work.

Multiple customers

Agencies and consultancies can give each end customer their own group, keeping their projects and data isolated from other customers in the same tenant.

Cross-functional teams

A user can belong to several groups at once, for example an executive who needs visibility into Sales, Marketing, and Operations.
If you don’t create any groups, Orion behaves exactly as before. Groups are an additive feature: your existing users, projects, and permissions are unaffected until you opt in by creating a group.

Accessing Groups

Group management lives alongside user management in Admin Settings → Users. The page has two tabs: Users and Groups.
Admin Settings with Users selected and the Manage Groups page open on the Groups tab, which is outlined in red, showing four group cards: Data Team, Leadership Reporting, Finance, and Operations

The Groups tab

Creating a Group

From the Groups tab, click + New Group. Give the group a clear name and an optional description.
New Group dialog over the Groups tab, with a Name field that has a Select Prefix picker, an optional Description field, and Cancel and Create group buttons

Create a group

If a non-admin user creates a group, they automatically become its first Group Admin. Tenant Admins who create groups manage them via their tenant role and are not added as members.

Naming Groups with Prefixes

When creating a group, the modal offers the option to select a prefix from the existing group names. Tenant Admins can also choose No prefix. Other users must pick a prefix. Prefixes are a purely organizational label: they make related groups sort and display together, but confer no shared access or functional relationship between groups. A group named Verizon / Sales and one named Verizon / Marketing are completely independent. The prefix only keeps them visually adjacent. The first group you create under a prefix acts as the catch-all group for that prefix, a landing zone you can add users to before their specific sub-group is ready. For example, you might create Verizon first, add new users there while you’re still setting up sub-groups, then move them into Verizon / Sales or Verizon / Marketing once those are configured.
Use prefixes consistently from the start. It is significantly harder to reorganize groups after members and projects have been added. A naming convention like [Customer] / [Team] or [Department] / [Sub-team] works well for most organizations.

Group Roles

Each user has a role within each group they belong to. A group role only controls what someone can do inside that group: it is separate from and independent of their tenant role.

Group Admin

Manage everything in the group: add and remove members, add projects, data sources, Context pages, and integrations, and delete the group.

Group Analyst

Full working access to everything in the group. Can create new projects and share them with others. Can also create new groups and automatically becomes the Admin of any group they create.

Group Viewer

Read-only access to the group’s projects, data, Context pages, and integrations. Cannot manage group settings or data source configuration. Warehouse queries and project document searches require viewer queries enabled.

Roles at a Glance

The table below covers the six roles you assign, across both levels, tenant and group. Tenant roles apply across the entire Orion instance; group roles apply only within the specific group.
  1. A Group Analyst automatically becomes Group Admin of any group they create.
  2. Extended Viewer Settings controls both warehouse queries and searches of documents uploaded to the project. It is off by default. See Extended Viewer Settings for how to enable it.
  3. Group Admins can invite new users to the tenant through the group’s Invite by email flow, or with Add User on Admin Settings → Users.
  4. A Group Admin can still open Admin Settings → Data Sources, Integrations, and Users: being a Group Admin in any group gives access to those sections. What they manage there is their own groups’ resources, not the tenant’s settings.
Tenant roles and group roles are independent. A tenant Viewer can be a Group Admin. A tenant Analyst can be a Group Viewer in one group and a Group Admin in another. Orion always evaluates the role that applies to the specific resource someone is trying to access, so what a user can do in chat, sharing, and editing may differ from one project to the next.

Users with roles across multiple groups

Tenant Admins always have full visibility across every group. For everyone else (tenant Analysts and Viewers), group roles can vary between groups. A user can simultaneously be:
  • A Group Admin in a group they created or were promoted in
  • A Group Analyst in a colleague’s group they were invited to contribute to
  • A Group Viewer in a third group where they only need read access
This means two users with the same tenant role may have very different effective access depending on which groups they belong to and what roles they hold there. When troubleshooting unexpected access, check both the user’s tenant role and their role within each relevant group.

Onboarding new users

Whether you’re adding an internal teammate or one of your customers, the safest default is the same: invite them as a tenant Viewer, then layer their real access on top through groups. A tenant Viewer is a blank canvas: they cannot see any projects, data sources, or Context pages by default. From there, add them to the right group(s) with a group role that matches what they need to do:
  • Group Viewer: read-only access to the group’s projects, data, Context, and integrations
  • Group Analyst: full working access; can create and share projects within the group
  • Group Admin: full administrative control of the group, including adding members
This keeps tenant-wide settings and any unrelated projects off-limits while giving the user everything they need inside their group. The pattern works equally well for an internal employee joining a single team and for a customer who should only see their own group’s projects. The Invite by email flow from inside a group is the fastest way to apply this pattern:
1

Open the group and start an Invite by email

From the group’s detail page, click Add member, then Invite by email at the bottom of the picker.
2

Pick the tenant role

Choose Viewer. This is the user’s baseline across the entire tenant and keeps everything outside their group off-limits.
3

Pick the group role

Choose Group Admin, Group Analyst, or Group Viewer based on what they need to do inside this group.
4

Send the invite

The invitee receives an email and, on first login, lands in Orion with both roles applied automatically.
Reserve tenant Admin and Analyst roles for people who genuinely need tenant-wide reach. For everyone else (internal or external), “tenant Viewer + Group [role]” is the safest default.

Managing a Group

Click any group from the Groups tab to open its detail view. From here you can manage everything the group has access to using the tabs along the top.
Detail view of the Data Team group on the Members tab, with the tab row outlined in red: Members, Projects, Data Sources, Context, Metrics Catalog, Integrations, and Settings, above a list of six members

Manage a group

The header shows who created the group and when. Click the group name or description to edit them inline.

Members

The Members tab lists everyone in the group along with their group role.

Adding existing users to a group

Click Add member to open the member picker. It lists the people you are allowed to add, so a Group Admin sees fewer users than a Tenant Admin does. If the person you need is missing, ask a Tenant Admin to add them. Pick the role they should have within the group, then add them.
Add members dialog with a search field and four tenant users, one selected with its group role picker set to Group Analyst and outlined in red, above an Add 1 member button

Add users to a group

Inviting new users directly into a group

If the user is not in the tenant yet, click Invite by email at the bottom of the picker. Select their tenant role first (Admin, Analyst, or Viewer), then their group role. Only tenant Admins pick the tenant role: a Group Admin’s invitee is always a Viewer. The invitee will receive an invitation email and, on first login, lands in Orion with both roles applied.
Inviting users directly into a group is the fastest way to onboard a new team or customer cohort. They land in Orion already configured with the right access, no second step required.

Changing a member’s role

Pick a different role in the Group Role select on the member’s row. There is no separate save step. Your own row is locked, whatever your role: another Group Admin or a Tenant Admin changes it for you. A group keeps at least one Group Admin. A Group Admin cannot demote or remove the last one, and the row stays as it was. A Tenant Admin can. The group is then left with no Group Admin, and only Tenant Admins can manage its members until you promote one.

Removing a member

Open the three-dot menu on the member’s row and select Remove from group. The person loses what the group gave them: its projects, data sources, Context pages, and integrations. A project they were invited to directly stays with them.

Projects

The Projects tab lists the group’s projects. Everyone in the group can access them with permissions matching their group role.
Data Team group on the Projects tab listing Customer Success, Supply Chain, Finance, and Marketing, with the Add project button outlined in red in the upper right

Projects available to a group

Click Add project to add more projects to the group. The picker shows projects you have access to.
Add projects dialog with a search field, a checkbox list of three projects (Program Management, Summit Civil Works, and Incident Management), a 0 selected counter, and Cancel and Add Projects buttons

Add projects to a group

A single project can belong to more than one group, useful for shared work that spans multiple teams.
Creating a new project does not automatically add it to a group. A project belongs only to the user who created it until a Group Admin or Group Analyst explicitly adds it to the group from this tab.

Data Sources

When a project is added to a group, the data sources attached to that project automatically become available to everyone in the group, so you don’t need to enable them separately. The Data Sources tab is additive: use it to expose data sources to the group beyond what its projects already provide.
Advisory group on the Data Sources tab, which is outlined in red, listing a Looker data source and a Snowflake data source, with an Add data source button in the upper right

Data sources available to a group

Context

The Context tab controls which Context pages and folders the group can use. You can select individual pages or whole folders. Each linked page also has an Auto-inject switch: when on, the page is automatically included in chat context for everyone in the group, with no per-project enablement needed. See Default Pages (Auto-Inject).
Data Team group on the Context tab listing three linked directories, with the Auto-inject column and its switches outlined in red

Context pages available to a group

Selecting a whole folder means any new pages added to that folder later are automatically available to the group. This is the easiest way to keep a department’s reference material in sync as it grows.

Metrics Catalog

The Metrics Catalog tab lists the catalog metrics and folders restricted to this group. Click Add metric to restrict more. See Restricting a metric to a group for how a restriction changes who sees a metric.

Integrations

The Integrations tab controls which integrations the group has access to.
Data Team group on the Integrations tab, which is outlined in red, listing a GitHub connection named Schema and a Notion connection named Team Notion, with an Add integration button

Integrations available to a group

How users get access to a project

A user can be given access to a project in two ways:
  1. Through a group: they’re a member of a group that the project belongs to. Their permissions match their role in the group.
  2. Directly: they were invited to the project individually from the project’s Share menu, independent of any group.
The two methods work side by side. Removing someone from a group doesn’t cancel any direct invite they have, and removing a direct invite doesn’t remove them from the group. The Project Settings modal shows which groups currently have access to the project, alongside its other settings.

Deleting a Group

To delete a group, open it, select the Settings tab, then click Delete Group. The group card’s … menu offers the same action.
The Data Team group's Settings tab in Admin Settings, with Delete Group outlined in red below the Danger zone heading

Delete a group from its Settings tab

The confirmation dialog summarizes what will happen:
Delete group Data Team dialog stating that six members will lose group access and nine projects will be unshared, with a field to type the group name and a disabled Delete group button

Delete a group

  • Members lose access to anything they only had through this group. They keep any direct project access they were granted individually.
  • Projects that are only used by this group can either be transferred to the group’s Admins (who keep access individually) or deleted along with the group.
  • Data Sources, Context pages, and Integrations are not deleted, they simply leave the group.
Type the group’s name to confirm, whether or not you also delete its projects.
Deleting a group is permanent. The group and its membership are gone for good. Members who had no other way to access projects will be left as Viewers with no projects to see until someone adds them again.