PricingConsole

When a member leaves

Last updated 12 November 2026

View .md

When a person leaves an organization, keep what they set up working, take them off it, and replace the keys they could still read. Removing a person is done in the console only. What happens at that moment is on When someone leaves.

Move their programs to Agents

Every key that acts as the person is revoked when they leave, so a program or job that runs on one stops. Give each one a key that acts as an Agent instead, and restart it with that key (see Add an Agent):

tonbo agent create release-bot
tonbo api-key create release-bot-ci --member release-bot

Make sure another person is an owner

An organization keeps at least one person as owner, so its last owner cannot leave. Find the members and their roles, and give another person the owner role; only an owner grants it. In the console, change the role on the person’s page under Members. With the CLI or the API:

tonbo member list
tonbo member update <member subject> --role owner

Remove them

An owner or an admin opens the person’s page under Members and chooses Remove from the organization; or the person chooses Leave organization on its Settings page. The CLI and the API have no step for either. Everything they created stays with the organization, including the Agents they created and those Agents’ keys.

Replace the keys they could read

The Agents’ keys keep working after the person leaves. Rotate each key they held a copy of, such as one they created for an Agent or read from your secret store (see Rotate a key). Listing the account’s keys shows who each acts as, and none of them acts as the person any more:

tonbo api-key list