Skip to Content
OpenInspect
Working in a session

Multiplayer and sharing

Choose session visibility, share private sessions with collaborators, and understand how ownership, team membership, and roles affect access.

Last reviewed View as MarkdownEdit on GitHubGive feedback

This page explains who can see and prompt a session, how to bring a colleague into one, and what each person's role lets them do.

Ownership and visibility

A session has fixed ownership and changeable visibility. It is either workspace-owned or owned by a team; making a team-owned session Workspace or Private visible does not transfer ownership. Non-members cannot act in a team-owned session, except to remove their own collaborator grant. The creating user is its session owner, which also matters for private access and sharing controls.

VisibilityWho can read, with session read permission
WorkspaceAdmitted workspace users, including Viewers.
TeamMembers of the owning team, plus workspace Administrators and Owners, when Teams enforcement is on. Requires an owning team.
PrivateThe owning user and explicit collaborators. Collaborators on team-owned sessions must remain current members of that team. Workspace Owners also have audited break-glass read access.

Check your deployment's enforcement mode

TEAMS_ENFORCEMENT defaults to shadow. In shadow or off, non-private Team visibility does not enforce read isolation from other workspace readers. Private access and team-owned non-read actions are enforced in every mode. Before relying on Team visibility to restrict readers, ask your operator to confirm on in Deployment.

A workspace Owner can open a private session by ID using audited break-glass access. That exception does not put the session in their lists or grant prompt or sandbox access. Administrators and team leads do not gain private access just from their role.

Participant labels record contributions; appearing in the timeline or Participants list does not grant access. Discovery filters such as Mine or Started by me are not access boundaries either. See Teams for membership and Inbox and search for discovery scopes.

Creating a session also requires permission to use its repository or environment, so a person may be able to open an existing session without being able to start a new one on the same repository.

Defaults and explicit private sessions

A team's default session visibility can be Team or Workspace, never Private. When no visibility is explicitly selected, normal session creation, Slack and Linear launchers, and automation runs use the owning team's current default, or Workspace when there is no owning team. The launch source does not override the default.

You can still explicitly choose Private in the new-session access selector or use an existing session's Visibility control when authorized. Private requires a workspace user owner and is allowed for both teamless and team-owned sessions. Creating a team-owned session requires current membership in that team; making it private does not bypass membership checks.

For deployments upgrading from private team defaults, migration 0085_team_default_visibility.sql changes those defaults to Team, including archived teams, and fences older application versions from writing private team defaults during rollout. Existing sessions and collaborator lists are unchanged. Operators must apply the migration before rolling out the narrowed team-default schema.

Sharing a session

Use Copy link (in the More menu above the composer on desktop, or in the "Session actions" menu on phones) to copy the session URL. Sending the link does not grant access: the recipient must already pass the session's access checks.

For a private session, an authorized owning user or workspace Owner can open Collaborators in the right sidebar, choose Add collaborator, and click Add. Use Remove to revoke a grant. Team-owned sessions accept only active current members of the owning team as collaborators. If a collaborator leaves that team, their stored grant no longer gives access. Managing collaborators on a team-owned session also requires current membership, even for the owning user or workspace Owner, except when removing your own grant. Collaborator status never grants team membership or a workspace role.

Collaborators still need the appropriate workspace permissions to prompt or use sandbox tools. A workspace Owner reading through audited break-glass access does not thereby gain collaboration or sandbox access: those require being the owning user or a collaborator. Other administrative actions remain subject to their own checks.

Once authorized, the other person sees the shared timeline and sandbox status. Private sessions cannot be published to Slack, and actorless bot services cannot read them, even if a user can.

Change visibility

  1. Open the session's right sidebar, or Details on a small screen.
  2. Review Include child sessions, which is checked by default. Clear it before changing visibility if you want to change only this session.
  3. If you are authorized, choose Workspace, Team, or Private under Visibility. The selection saves automatically after any required confirmation; there is no separate Save button. Team requires an owning team; Private requires an owning user.

Including children when applying Workspace or Team shows a confirmation: private child sessions will also change to that visibility. Team visibility also requires confirmation when changing only the parent, because the owning user may lose read access if they no longer belong to the team. Cancelling leaves visibility unchanged.

Unchecking Include child sessions saves nothing; it only scopes later changes to this session. Checking it again immediately applies the current visibility to descendants, after any required confirmation, even if the parent's visibility has not changed.

Controls are disabled while Updating... is shown. You must be authorized for every included descendant. A failed save normally restores the previous selection; when Retry without child sessions is offered, the failed selection is retained so the retry can apply it only to the parent.

For non-private sessions, the owning user, owning team's leads, and workspace administrators can change visibility if they meet the access checks. For private sessions, that authority is limited to the owning user or workspace Owner. Team-owned changes always require current owning-team membership. Visibility changes never change ownership.

Presence

The Participants section at the top of the right sidebar shows who is in the session: an avatar for each participant (up to four) and a count such as "2 prompt engineers". A green dot on an avatar means that person is connected right now. Presence updates live as people open and close the page.

Everyone connected receives the same event stream, so a prompt sent by one person and the agent's response to it appear for all participants at the same time.

Prompt attribution

Each prompt in the timeline is labeled with its author: "You" for your own prompts, and the other person's name and avatar for theirs. The attribution is carried all the way into git. Commits the agent makes while working on a prompt use that prompt author's SCM name and email as the commit author, so a branch that two people steered has both of them in its history. Pull requests are opened with the prompting user's GitHub identity when one is connected. See reviewing changes for how attribution and commit signing interact.

Prompts queued by PR Feedback Autofix carry a "Resumed by PR feedback" header that names the source (a review or a PR comment, from a human or a bot).

Collaboration patterns

  • Start and steer. One person writes the initial prompt and moves on. A colleague opens the link later, reads the timeline, and sends the follow-up that corrects course. Follow-ups queue behind the running turn regardless of who sent them.
  • Pair debugging. Two people watch the same run. One reads tool output in the timeline while the other checks the diff in the Changes panel, and either can stop the turn if it goes wrong.
  • Hand-off. Share the link at the end of your day. The next person sees the full history, the queued prompts, and the current sandbox state, and continues in the same branch.
  • Teaching. Newer team members can read sessions they have access to and see how others prompt and how the agent works through a task.

Because follow-ups are queued in order, agree on who is steering before both of you send corrections at once. The queued prompt stack above the composer shows what is waiting, and anyone authorized for that session's lifecycle actions can remove a queued prompt.

What not to put in a session

People authorized to read a session, including eligible Viewers, can see its recorded content:

  • The text of every prompt and every attached image.
  • The agent's responses, tool calls, and command output, including anything printed by a script.
  • Screenshots and recordings.
  • The diff and the branch.

Choose visibility before adding sensitive content, and remember that it can be widened later, including through a parent session's visibility change. Do not ask the agent to print secrets in the sandbox. Keep credentials in Secrets rather than prompts; configured secrets are injected as environment variables, and a command that echoes one puts its value in the timeline.

Role effects inside a session

Workspace roles grant feature permissions, not unconditional access to every session. The table describes built-in permissions after the session's visibility and membership checks pass.

RoleIn a session
ViewerRead only. Can open the session, watch the timeline, and read the diff and media. Cannot prompt, stop, rename, archive, or use sandbox tools.
MemberCan prompt and contribute, and can stop turns, remove queued prompts, rename, archive and unarchive (sessions.lifecycle), retry a failed diff, and use the terminal, code-server, VNC, and tunnels (sessions.sandbox_access).
Administrator and OwnerMember feature permissions plus workspace administration, still subject to session access checks.

Lifecycle actions (stop, rename, archive, unarchive, remove a queued prompt, retry the diff) need sessions.lifecycle. Prompting needs sessions.collaborate. Sandbox tools need sessions.sandbox_access. Except for collaborator self-removal, every non-read action on a team-owned session requires current owning-team membership, including for its owning user, Administrators, and Owners. Private prompting and sandbox access additionally require being the owning user or a collaborator.

Role changes and suspensions take effect on the next request. A browser that already has the session open is rechecked at least every five minutes, so someone whose access was removed can keep a live connection for up to five minutes.

Troubleshooting

SymptomCauseFix
The Sessions page says "You do not have permission to view sessions."Your account holds no role that can read sessions. Every built-in role, Viewer included, can, so your workspace access has been removed or suspended.Ask a workspace Owner or Administrator to check your account under Settings › Workspace access.
A colleague cannot open a session linkThe session's visibility excludes them, or their team-owned collaborator grant no longer applies.Check the audience and their current team membership; for Private, ask the session owner to add them as a collaborator.
A person whose access was removed or suspended still sees live updates in an open sessionLive connections are rechecked at least every five minutes, not on every event.Wait up to five minutes; the connection closes on the next recheck. New requests are refused immediately.
A session link is unavailable, or you can read but cannot actVisibility, collaborator status, team membership, or feature permissions do not allow the operationAsk the owning user or team lead to check access. Administrator status alone does not bypass team action checks.

Next steps

On this page