Set up your organization so the whole team’s agent work lands in one shared workspace. This page covers organizations, members, and visibility; day-to-day navigation of the shared session list is the Team workspace page.
Organizations
An organization is the boundary for everything in paper: sessions, search, Insights, Skills, gateways, and membership are all scoped to exactly one org. If you belong to several, switch between them in the console header — the workspace refreshes to the selected org — and set which one paperctl routes through with paperctl org select.
Creating one: the first person on a team names the org at console.papercompute.com/onboarding/org. Onboarding provisions a default gateway and backends so captures route without further setup.
Members and roles
Roles come from your organization’s directory: members use the workspace; admins also manage it — invitations, member removal, and billing are admin actions.
Bring people in from Settings → Team in paper console: send an invitation to each teammate’s email. Pending invitations are listed on the same page and can be revoked before they’re accepted. New members join as member; admins can grant the admin role. Settings → Team also shows your organization’s ID and slug — useful when support or scripts ask for them.
When an invited teammate accepts and runs paperctl login, the org is pre-selected and the CLI discovers the default gateway on its own — the quickstart is the whole setup for them.
There is also a CLI command, paperctl org membership add, but it’s for automation rather than people: it takes an internal WorkOS user id instead of an email, plus an explicit --org-slug and the admin role. For adding teammates, the email invitation is the path — the command reference covers the CLI command’s requirements if you’re scripting.
What members can see and do
- Sessions are visible organization-wide: every member can open, export, and delete any of the org’s sessions. (Export is included on plans with session export — see Settings → Billing for your plan.)
- Published Skills are visible to everyone in the organization.
- Gateways and backends are configured by admins — see Backends and providers for routing and shared provider keys.
Plan capture with that in mind: the organization is the unit of visibility, so a session belongs to the whole team the moment it’s captured.