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.

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 connection with them — and revoking their dashboard access does not revoke the credential your Worker trusts. Those are two separate acts, deliberately.

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 rather than owned per Worker, so a second connection to a sibling would be a second credential onto the same rows.

Teams are a paid surface

Members and roles, a shared record of who did what, and notifications fanned out are what the Team plan adds.

Free and Solo are one person. The connection model does not change — what changes is how many people can act through it, and whether the record distinguishes them.

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.

ESC