Members and roles are what the Team plan adds.
Inviting
Roles and permissions is what you are handing over, organizations and teams is the container, notifications is what they will hear about, and plans and pricing is what a seat costs.
By email. They sign in passwordlessly, the same way you did — there is no password to set and none to reset.
What a new member gets
Access to the organization’s connections, bounded by their role in the UI and by the connection’s scopes on your Worker.
Not a credential of their own. The connection’s keypair belongs to the organization, and adding a person does not mint a second one.
What the record shows
Every administrative action carries the dashboard user’s own subject, alongside the connection id.
So a shared credential still distinguishes who acted — which is exactly the property a team needs and a single-user account does not.
A shared record of who did what, and when is one of the things the Team plan is for.
Removing somebody
Their member record lists every agent they authorized, read live from each of the organization’s projects and stored nowhere here: its purpose, what it acts as, its credential, its scopes with their kinds, when it was registered and when it was last observed. A trust is shown as one they sanctioned, not one they use. Connections registered before principals were recorded are listed apart as unattributed, and matched to nobody.
Removing them settles those agents. The confirmation says how many agent credentials the removal revokes and when they last ran, before it does anything. Each is revoked on its Worker, or handed to a member still here whose role covers it. Leaving one running with nobody to answer for it is not offered, and each revocation and each hand-off is audited.
A demotion is the same event, one size smaller. Making an admin a member lists every agent the new role does not cover, and each is revoked or handed on. A hand-off is re-checked on every later role change and removal, and an ownership transfer that leaves the old owner an admin settles theirs the same way.
Somebody with agents running cannot simply leave. They are asked to have an admin remove them, which revokes or hands those agents on.
What this cannot see. Anyone with a project’s Cloudflare sign-in can register an agent outside this dashboard. That is not prevented here. It is re-checked on every read and on every change of role.
The organization’s own connection is a separate act, deliberately. Revoking their dashboard access does not revoke the credential your Worker trusts for the dashboard. The connection belongs to the organization, so somebody leaving does not take it with them — and if you want the credential rotated as well, that is rotate and revoke.
The one rule worth agreeing on first
Who may grant an entitlement.
Grant mints paid product out of nothing. It is the action most worth restricting, and it is a separate scope from revoke precisely so a refund tool never has it. In the dashboard both are charges calls, which only the owner’s role covers.
Notifications fan out
Security and release notifications reach one person on Solo, and a team on Team.
Alerts, checked hourly against your Workers, are the other half — and both are about the same thing: somebody finding out before a customer does.
What we store about your team
Our own users and organizations. Their names, their addresses, their roles.
Not your users. Yours live in your D1 and are fetched live.