Organizations and teams

What an organization is

Inviting your team is how people get in, roles and permissions is what they can do, connections are per environment, and the audit trail is what records who did what.

The thing that owns your connections and your subscription.

A person belongs to one. One person can belong to several — which is exactly why who did this and whose account it was done to are two different questions.

Belonging to several means a chooser. It asks by id and shows the display name, because a slug means nothing to somebody deciding which company they are looking at. The membership is proved in the same statement that records the choice, so naming an account there buys no reach — it only says which of your own to draw. The chooser and the home route render the same component for the state where you belong to nothing, so the two screens that can report it cannot drift apart.

The tenancy model is the kit’s own, @pithy-sh/organization, the same capability pithy add organization scaffolds into your project. This dashboard was where it was designed and it now composes it like any other adopter. What stays this product’s is the role catalog — the matrix of who may do what — because that is the adopter’s to write.

Why that distinction matters

The actor answers who. The tenant answers for whom.

They differ the moment one person administers two accounts: every event they produce carries the same actor, so a trail scoped by actor returns somebody else’s history.

And it cannot be derived later. The tenant of an action is a fact at the time of the action; membership is a fact now.

Read a membership table for it afterwards and somebody who joins today retroactively owns a year of another organization’s trail — while somebody who leaves takes theirs with them, exactly when it is most wanted.

Connections belong to the organization

Not to the person who ran pithy dashboard connect.

So somebody leaving does not take the dashboard’s connection with them. An agent they authorized is different, because it is bound to them. Their member record lists every agent credential they sanctioned, and removing them, or demoting them below what an agent needs, first shows the agents it reaches, then revokes each one or hands it to a member whose role covers it. Nothing they authorized is left running on authority they no longer have.

One connection per project and environment

A customer may register several projects, each with its own keypair.

Sibling Workers are not separately addressable, and that is deliberate: the data being administered is shared through binding names by default, so a second connection to a sibling would be a second credential onto the same rows. A Worker that owns its database through ownBindings is the exception: the connection reaches one app database per environment, so it covers one of the two.

Seats are free; the Team plan adds working together

Every plan has unlimited seats, Free included. Nobody pays per head to administer a system they own, so inviting people and giving them roles is not what a plan sells.

What Team adds is what several people do at once: notifications fanned out, one message to every person who asked for it, where Solo’s reach the owner only; shared triage of the support inbox; and an audit explorer that searches the record by actor, action, outcome and range. The connection model does not change on any plan.

What we store about your organization

Our own users and organizations. Our own subscriptions. Connection metadata — project, environment, endpoint, credential reference.

Not your users. Yours are in your D1, fetched live and discarded.

Deleting an organization cascades. It reaches every table that holds something of that account’s, named one by one rather than swept by prefix, and a test fails when a table is dropped from the list — a row missed here is a row that outlives the account it belonged to.

ESC