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.
Bring people in from Settings in paper console — send an invitation to their email — or from the CLI:
paperctl org membership add [email protected]
paperctl org membership add [email protected] --role adminAdding members requires the admin role. New members join as member; --role admin grants admin. Pending invitations are listed in Settings and can be revoked there before they’re accepted. When an invited teammate runs paperctl login, the org is pre-selected and the CLI discovers the default gateway on its own.
What members can see and do
- Sessions are visible organization-wide: every member can open, export, and delete any of the org’s sessions.
- Published Skills are visible to everyone in the organization.
- Gateways and backends are configured by admins — see Custom backends 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.