// docs / collaboration

One library, several people.

A repository can be shared with teammates without making it public. Invites are links you copy — no email required on their side beyond signing in.

Inviting someone

Open the repository → click the collaborators icon next to its name → enter their email and pick a role. You get an invite link to copy and send however you like (Slack, DM, carrier pigeon). They open the link, sign in with that email, and the repo appears in their sidebar under Shared with you.

Roles

roles

viewer   read prompts and history
editor   + create and edit prompts, commit versions
admin    + delete prompts, manage collaborators
owner    + repository settings, visibility, deletion

Every permission is enforced server-side, not just hidden in the UI. Owners and admins manage the member list from the same collaborators dialog; members can leave a repository themselves.

Working in a shared repo

Shared repositories behave exactly like your own: same editor, same version history, same CLI access. Commits record who saved each version, and the editor shows when the latest version was written by someone else — history is one timeline for the whole team. Prompt and repo counts respect roles everywhere (web, CLI, extension, MCP), because they all read the same API.

Where to go next

Sharing with the world instead of a team? Sharing & discovery. Wiring the library into your agents? MCP server.