Skip to main content
Bringing a teammate into your sandbox gives them access to everything inside it — the data sources, the OAuth’d integrations, the agents, the runs, the knowledge graph. They sign in as themselves; the sandbox shows up alongside their own work. This is the right choice when you and the teammate are going to build alongside each other, not just hand off one finished thing.

​
Pick a role

RoleThey can readThey can buildThey can destroy
EditorEverythingYes — new agents, new sources, new triggersNo
ViewerEverythingNoNo
Both roles can run any agent in the sandbox. The difference is whether they can change things. Destructive operations (archive, delete, disconnect) stay with you — collaborators cannot remove agents, sources, or the sandbox itself. The asymmetry is deliberate; one person should hold that authority.

​
Invite someone

The fastest path is to ask the Concierge:
“Invite @alice as an editor on this sandbox.” “Give @bob viewer access for the next 30 days.” “Add @carol as editor, but only for the marketing project.”
You can scope an invite three ways:
  • Project-scoped — only one project inside the sandbox, useful when one sandbox holds work for several teams.
  • Time-boxed — automatic expiry, useful for contractors and short-term collaborations.
  • Sandbox-wide and indefinite — the default.

​
What your teammate experiences

  • They sign in to their own Copass account as themselves. No new tokens to manage.
  • The shared sandbox appears in their workspace list with a role tag (editor / viewer).
  • Their personal integrations (their Slack, their GitHub) stay theirs and don’t merge with yours.
  • Anything they do inside the shared sandbox is billed to your account, not theirs.
  • If they’re a viewer, the parts of the UI that would let them change things are simply not there.

​
Common patterns

Whole-team read access

Invite every teammate as a viewer. They can browse agents, run retrieval, watch runs — but the build surface is yours.

Per-project editor

Scope an editor invite to one project so a collaborator only sees and changes the slice that’s theirs.

Time-boxed contractor

Invite as editor with an expiry date set to the contract end. Access flips off automatically — no calendar reminders.

Cross-team observer

Viewer access for security or platform teams that need to audit your agents and runs without changing anything.

​
Listing and revoking

“Who has access to this sandbox?” “Revoke @alice’s access.”
Both are owner-only. Revocations take effect immediately. The audit trail (who you invited, when, who revoked, when) is kept for you to review.

​
When to share an agent instead

If the person you’re sharing with only needs to run one specific agent — a customer using your support agent, an embedded widget on a marketing site — share the single agent instead of the whole sandbox. Sandbox connections are for collaboration on the whole tenancy; agent shares are for narrow, single-purpose access. See Sharing agents.

​
Next steps

  • Sharing agents — give someone access to one agent without sharing the whole sandbox.
  • Concierge — the natural-language interface for every invite, list, and revoke action above.
  • Sandboxes — the tenancy model these invites sit on top of.