Skip to Content
OpenInspect
Administration

Workspace access and roles

How people are admitted to an OpenInspect workspace, what each role can do, and how Owners and Administrators manage members.

Last reviewed View as MarkdownEdit on GitHubGive feedback

This page explains who can get into your workspace, what each role permits, and how to change or suspend a member from Settings › Workspace access.

Settings, Workspace access: a members list with role dropdowns and Suspend buttons, and role cards for Administrator, Member, Owner, and Viewer
Settings › Workspace access: one role per member, with the four roles described below the list.

One workspace, one trusted organization

An OpenInspect deployment is a single workspace. The source-control App installation defines which repositories the workspace can reach. Roles control which OpenInspect features a person can use; they are not per-repository access lists. Team membership, repository grants, resource ownership, and session visibility add resource-specific checks. See Teams and Security and trust model.

Signing in and admission

A deployment can offer GitHub sign-in, Google sign-in, or both. The sign-in page shows only the providers the operator configured.

Signing in has two stages:

  1. Your identity provider verifies your identity and email address.
  2. The workspace's admission rules decide whether you may join the workspace. They come from the deployment configuration and from Settings › Workspace access › Who can sign in.

Admission can be limited by any of the following, set by the operator in the deployment configuration or by an Owner or Administrator under Who can sign in:

Allowlist kindWhat it matches
GitHub usernameThe signed-in GitHub login
Verified email addressAn exact address
Verified email domainAny address on the domain
Allowed GitHub organizationActive membership in the organization

These rules are checked at sign-in. Removing someone from an allowlist or from a GitHub organization does not end an existing browser session. When access must be revoked immediately, suspend the member (see Suspension).

Signing in does not make anyone an Owner or Administrator. Every admitted user has exactly one workspace role, and new users receive the Member role by default.

Managing who can sign in

Owners and Administrators add sign-in rules under Settings › Workspace access › Who can sign in. Custom roles cannot see or edit this list, even with member-management permission.

  1. Type an email address, an email domain, or a GitHub name into Add an email, domain, or GitHub name. For a bare name, choose whether it is a GitHub user or a GitHub organization.
  2. Click Review and save, check the changes, and click Save changes.

Rules marked with a lock come from the deployment configuration and stay in effect whatever you change here. Rules added in Settings extend the deployment's rules; they cannot narrow them. You can add at most 50 rules, and GitHub organizations are limited to 10 in total, counting the deployment's (or to the deployment's own count, if it already has more). Adding a rule sends no invitation. While the operator has unsafe allow-all set, the list is read-only. Each save is recorded in the audit log as Sign-in allowlist updated.

Joining through a bot

New users joining through Slack or Linear must provide a bot-attested email that matches an allowed email or email domain, from the deployment configuration or from Who can sign in. When only GitHub usernames or organizations are allowed, sign in on the web first, then use the same account email in Slack or Linear. GitHub bot actors must already be known to the workspace. An operator's explicit unsafe allow-all setting permits new users only when every deployment and Settings allowlist is empty.

Known bot actors and new actors linking to an existing account by attested email keep its role and suspension; they do not repeat admission. Newly admitted bot users receive Member. A bot cannot enroll a new Slack or Linear actor without an email, including external Slack Connect users whose emails it cannot read.

If the bot reports that your account is not authorized to join, ask an administrator to check the admission rules or sign in on the web with the email on your bot profile. Two different emails that both pass admission can still create separate accounts; an administrator can merge duplicate member accounts.

Roles

OpenInspect has four built-in roles. This table describes workspace feature permissions, not unconditional access to every resource. The session, automation, and environment rules below also apply.

CapabilityOwnerAdministratorMemberViewer
View repositories and environmentsYesYesYesYes
Use repositories and environments in sessionsYesYesYesNo
Manage shared settings, integrations, and secretsYesYesNoNo
Create sessionsYesYesYesNo
Read sessions permitted by visibility rulesYesYesYesYes
Collaborate in and manage permitted sessionsYesYesYesNo
View automationsYesYesYesYes
Create automationsYesYesYesNo
Manage and trigger automations as executor or team leadYesYesYesNo
Manage and trigger any automationYesYesNoNo
View and manage workspace membersYesYesNoNo
Merge duplicate member accountsYesYesNoNo
View the audit logYesYesNoNo
Govern personal access tokensYesYesNoNo
Transfer workspace ownershipYesNoNoNo
View analyticsYesYesYesYes
View provider accountsYesYesYesNo
View image-build historyYesYesYesYes
Manage personal skill profilesYesYesYesNo

Owner. All workspace feature permissions, subject to resource-specific checks. Owners have audited break-glass read access to private sessions by session ID, but do not automatically gain collaboration or sandbox access. Only Owners can grant or remove the Owner role or suspend and restore another Owner. The final active Owner cannot be suspended or demoted, so the workspace cannot lose all ownership by accident.

Administrator. Runs the workspace day to day: members (including merging duplicate accounts), permitted sessions, automations, repositories, environments, provider accounts, integrations, secrets, personal access token policy, and the audit log. Administrators need session ownership or an explicit collaborator grant to access a private session. They cannot transfer ownership, change who holds the Owner role, or suspend and restore an Owner.

Member. Creates and uses eligible sessions, repositories, environments, and automations. Members manage and manually trigger automations for which they are the executor or an owning-team lead. Team leads also have team-specific administration capabilities; that does not grant workspace-wide configuration access. Members can view analytics.

Viewer. Read access to eligible sessions, automations, repositories, and environments, plus shared analytics, skills, and MCP servers. The workspace role does not permit session creation or prompting, sandbox access, personal skill-profile management, automation triggering, or shared configuration changes. Team-lead capabilities are separate from the workspace role.

How session access works

Session ownership and visibility are separate. Ownership is fixed at creation; a team-owned session remains team-owned even when its visibility is Workspace.

  • Workspace visibility allows workspace users with session read permission to read the session.
  • Team visibility limits reads to owning-team members and workspace Administrators/Owners when Teams enforcement is on. Non-private read isolation is not fully enforced in off or the default shadow mode; see Teams enforcement.
  • Private visibility permits the session owner and explicit collaborators. A collaborator on a team-owned session must still belong to that team. Private access is enforced in every mode.
  • Except for collaborator self-removal, every non-read action on a team-owned session requires current owning-team membership, including for Administrators and Owners. Feature permissions and action-specific checks still apply; being able to read does not grant collaboration, lifecycle, deletion, or sandbox access.
  • A workspace Owner, but not an Administrator, can read another person's private session through audited break-glass access. That read does not make the Owner a collaborator or grant sandbox access, and it does not bypass membership requirements for team-owned session actions.

The recorded session owner matters for private access and sharing controls. Participant labels grant nothing. The Mine filter and team discovery scope help find sessions; neither is a substitute for authorization. See Multiplayer and sharing for defaults, private collaborators, and sharing controls.

Creating a session also requires permission to use the selected repository or environment. A role can therefore view an existing session without being allowed to create a new one.

New HTTP requests reflect role changes and suspension immediately. Live browser connections to a session are rechecked at least every five minutes, so an open connection can remain for up to five minutes after access changes. Nobody needs to recreate the session.

How automation access works

Workspace-owned automation definitions are readable with automation read permission. Team-owned definitions require that permission plus owning-team membership or workspace Administrator/Owner status. Run history does not grant access to linked sessions: unreadable session IDs, titles, and artifact summaries are redacted.

The owning team and executor are different identities. The executor is the canonical workspace user whose authority is used for scheduled and event-driven runs, initially the creator. With the relevant feature permission, the executor or an owning-team lead can manage and trigger an eligible automation; Administrators and Owners have workspace-wide management and trigger permissions. Manual execution still requires the requester to qualify for the resulting session.

Creating an automation also requires sessions.create because the creator is its initial executor. Later scheduled and event-driven runs use the configured executor, which can be reassigned.

Run typeRuns under whose authority
Scheduled and event-drivenThe configured executor. At run time the executor must be active, allowed to create sessions and use the selected targets, and, for team automations, a current member of the active owning team. Target repository grants are rechecked.
Manual (Trigger Now)The person who clicked Trigger Now, even when an Administrator or Owner triggers someone else's automation. The requester must be allowed to trigger it and to create the resulting session; their identity is used, including for commit attribution. Pull requests the run's own prompt opens are created by the GitHub App.

Generated sessions inherit the automation's owning team and that team's current default visibility. A team lead or workspace Administrator/Owner with automation management access can reassign the executor through PATCH /automations/:id with { "userId": "<canonical-user-id>" }. The replacement must qualify to execute the automation. Being the current executor alone does not authorize reassignment. See Automations.

How environment access works

Workspace environments use workspace feature permissions. Team environments additionally require owning-team membership or workspace Administrator/Owner status to read or use; managing them requires environments.manage plus owning-team lead or workspace Administrator/Owner status. A team environment can launch only into a session owned by the same team. Eligible workspace environments can also appear in a team's session catalog.

Environment secret writes/imports/deletes, settings changes, and image-build actions require environment management access as well as their respective feature permission (environments.secrets.manage, environments.settings.manage, or environments.images.manage). This includes workspace environments: a custom role with only a feature permission is insufficient. Secret-key listing instead requires the secrets permission and environment read access; it never returns values.

The workspace's require-team-on-create policy applies to new sessions, environment definitions, and automation definitions. It does not by itself prohibit runs of existing workspace-owned automations. See Teams.

Bots and integrations

The Slack, GitHub, and Linear integrations act on behalf of a workspace user when they handle that user's request. Their effective access is limited by both the acting user's current role and the integration's fixed set of allowed operations. An integration cannot bypass a suspended user or perform workspace administration just because the acting user is an Owner. Calls that do not identify an acting user are denied unless a specific integration route explicitly permits that operation.

Integrations also apply their own ingress rules. The GitHub integration, for example, can require an allowed trigger user or sufficient repository collaborator access before it sends a request to OpenInspect. See Integrations.

Suspension

There is no action to remove a member from the workspace; suspension is the way to take someone's access away. Suspending a member disables their access without deleting their account or historical attribution. After suspension:

  • New browser, bot, and personal access token requests are denied.
  • Existing browser sign-in sessions are invalidated.
  • Live browser session connections close within five minutes.
  • Scheduled and event-driven automations using the member as executor no longer pass run authorization.
  • Existing session history and authorship remain intact.

Suspension does not stop a sandbox that is already executing. A user with the required session action access can stop or archive it separately; Administrators and Owners still need membership for team-owned session actions.

Managing members

Owners and Administrators manage members from Settings › Workspace access. The page lists each member with their display name, email, assigned role, and a Suspend or Restore button, followed by a Roles section showing each role, its description, and how many members hold it.

Review members and roles

Open Settings › Workspace access. Each row shows the member's current role. The Roles section below lists the built-in roles with their assignment counts.

Change a member's role

Choose a new role from the drop-down on the member's row. The change is applied immediately and recorded in the audit log. Only an Owner sees the Owner option, and only an Owner can change another Owner's role.

Suspend or restore a member

Click Suspend to disable access, or Restore to reinstate a suspended member. The button is disabled for an Owner when you are not an Owner yourself, and for the last active Owner.

Rules that apply regardless of who is signed in:

  • Only an Owner can assign or remove the Owner role or suspend and restore another Owner.
  • The last active Owner cannot be suspended or demoted. Promote a second Owner first.

Merging duplicate accounts

One person can end up with two member accounts. The most common case is a Slack account and a GitHub account that use different email addresses: the Slack integration creates an account for the Slack user, and GitHub sign-in creates another. Merging folds one account into the other so the person has a single identity, history, and set of settings.

Owners and Administrators merge accounts from Settings › Workspace access by clicking Merge accounts above the members list. The permission (workspace.members.merge) belongs to the built-in Owner and Administrator roles and can also be granted to a custom role. A custom role also needs workspace.members.read to review a merge, because the review shows both members' details and linked sign-ins. Grant it carefully: a merge moves sign-in identities between accounts, so whoever signs in with the merged-in account's identities signs in as the kept account. Merging Owner accounts always requires an Owner.

Choose the accounts

Pick the account to keep and the account to merge in. Keep the account the person signs in with; its role, email, and sign-in stay as they are. Use Swap if you picked them the wrong way round.

Review the merge

Click Review merge. Nothing changes yet. The review shows both accounts with their linked sign-ins (for example, GitHub · octocat and Slack) and what moves to the kept account: linked sign-ins, sessions, automations, team memberships, memories, skill profiles, and source-control and model-provider connections. The review also spells out what changes besides moving records:

  • Access changes. If the merged-in account leads a team where the kept account is only a member, the kept account becomes a lead of that team.
  • Combined skill profiles. A skill profile with the same name as one on the kept account is combined into it.
  • Discarded settings. Where both accounts have memory preferences or keyboard shortcuts, the kept account's stay and the merged-in account's are discarded.
  • Duplicates. Records identical to ones the kept account already has, such as membership of the same team or read markers for the same session, are dropped rather than duplicated.

Confirm

Tick the confirmation and click Merge accounts. The merge is applied in one step: either everything moves or nothing does. The merged-in account is deleted and signed out of the browser, its personal access tokens are deleted, its Slack or other linked identities now resolve to the kept account, and a workspace.user_merged event naming you as the actor is written to the audit log. A merge cannot be undone.

The review blocks a merge until these conditions hold:

  • Both accounts have the same role. If they differ, close the dialog, change one account's role in the members list, and review the merge again.
  • Both accounts are active, or both are suspended.
  • You are not merging away the account you are signed in with. Keep your own account and merge the other one into it.
  • Only an Owner can merge Owner accounts, and the kept Owner account must be active. Without that right, the review also hides the linked sign-ins of Owner accounts.
  • At most one account has a GitHub sign-in. An account can have only one GitHub identity, so two accounts that each sign in with GitHub can't be merged.

The review does not check personal MCP connections, but the merge fails with an error, and nothing changes, while either account has a live connection under Settings › Connections. Personal connections never move between accounts. Have the person disconnect first, or disable the server and use Revoke connections in Settings › MCP Servers, then merge.

If either account or your own access changes while you review (a role, suspension, the merged-in account's email, or a new GitHub sign-in), the merge is refused, nothing changes, and the refusal is recorded in the audit log. Review it again. If a merge succeeded but your browser lost the response, merging the same two accounts again reports success without changing anything.

Initial Owner bootstrap

The first person to sign in receives the Member role and is not promoted automatically. On a new deployment, the intended Owner signs in once, and a deployment operator runs the Owner bootstrap command with that person's user ID. This is an operator step; see the self-hosting guide and Deployment overview.

Troubleshooting

Next steps

On this page