Leaving an organization now ends its CLI and MCP access
When someone leaves or is removed from your organization, the tokens their `ah login` and MCP connections hold for it stop working right away.
Removing someone from your organization in the dashboard took away their dashboard access,
but any ah login they had run, and any MCP client they had connected, kept reading your
organization's data. Those tokens were checked against our own records, and nothing updated
those records when the membership ended. An admin had to find each one on the Tokens page
and revoke it by hand.
Now, when a membership ends, we revoke the tokens that person's logins minted for your organization. Deleting a user's account revokes the tokens it minted in every organization. Their access to other organizations is untouched. A connected MCP client keeps working for the organizations they still belong to and notes the one they left.
Tokens created on the Tokens page are not affected. Those belong to the organization, often as a backend's key, and keep working after the person who created them leaves. Revoke one there if it should go too.