Skip to content

Teams and organizations

An organization owns members, projects and billing. Your first sign-in creates a personal one. A team shares one organization and every member’s agents read and write the same memory.

From the console’s Org page, or:

meshpoint org invite alice@example.com # member
meshpoint org invite alice@example.com --role admin # admin
meshpoint org invite alice@example.com --role owner # owner
meshpoint org invites # pending

Admins and owners invite. Only owners hand out the admin and owner roles. The invite is matched by email: the person signs in at app.meshpoint.dev with that address through Google, Microsoft or an email code, and joins at that sign-in. The email they receive carries a link that steers the browser to the right organization, but signing in without the link works too. Seats are checked when the invite is created; see Plans.

Organizations that sign in through a WorkOS organization (enterprise SSO) add members on their first sign-in without an invite; the first member becomes owner.

Three roles. Your first sign-in makes you the owner of your own organization.

Member Admin Owner
Read and write items, capture sessions, fork yes yes yes
See the console: projects, memory, live activity yes yes yes
See and revoke sessions own only everyone’s everyone’s
Invite and remove members members only anyone
Invite admins and owners yes
Rotate signing keys, export data yes yes
Change roles yes
Billing, delete the organization yes

Owners change roles from the Org page’s role menu, or:

meshpoint org role <user-id> admin

Ownership moves by promoting someone to owner, then stepping down. The last owner cannot step down, so an organization always has one.

A person can belong to several organizations and switches between them at sign-in. meshpoint login --org <id> picks one for the CLI.

Every meshpoint login creates a session for one agent, named cli-<hostname> by default (--agent <name> to change it). A session holds a 7-day token refreshed with a 90-day refresh secret. The Org page lists them; so does the CLI:

meshpoint org sessions # yours; everyone's for admins and owners
meshpoint org revoke <session-id>
meshpoint logout # revokes this machine's session

Removing a member revokes their sessions in the organization:

meshpoint org remove <user-id>

A member whose account belongs to no other organization keeps a sign-in but no data.

Tokens are signed with the organization’s own Ed25519 key. Owners can rotate it:

meshpoint org rotate-key # old tokens die within about two minutes; sessions refresh onto the new key
meshpoint org rotate-key --revoke-sessions # and everyone signs in again
meshpoint org projects

lists every repository the organization has written to, recorded on its first write. Project ids are host--owner--repo; see How it works. Forks of a repository with their own origin are separate projects; the console’s fork form copies a branch’s items (or everything) into another project.

Owners delete the organization from the bottom of the console’s Org page. Type the organization’s name to confirm. Everything goes at once: projects, items, raw turns, keys, sessions, invites, the billing record (which cancels any subscription), and the accounts of members who belong to no other organization. Tokens already issued stop verifying within about two minutes.

Deletion is immediate and not reversible from the console. A point-in-time database copy kept by the hosting provider for disaster recovery expires within 30 days.

The API form is DELETE /v1/org with {"confirm": "<org name>"}; see the HTTP API.