A RichAPI workspace holds the API keys and the usage history of a team. The credit balance belongs to the organization. To leave a workspace, ask an Owner to remove you from the Members tab of the Organization page. The dashboard shows no Leave Team button and no Transfer Ownership button. An Owner promotes a new Owner with the Update Role action, and support completes the handover.

The RichAPI dashboard holds no control that removes your own membership. An Owner of the workspace removes you.

The Owner selects the actions menu at the end of your row, selects Remove from Account, and confirms with Remove User from Team. For the full procedure and the role rules, read Managing Workspace Members and Permissions.

Your access ends at once. The workspace disappears from the account switcher in the sidebar. To return, you need a new invitation from an Owner.

If the workspace holds no Owner who answers you, write to [email protected]. Name the workspace URL and the email address on your RichAPI account.

The Settings page at https://app.richapi.ai/home/<workspace-url>/settings has two tabs, Profile and Team. The Team tab shows two cards. It shows no Danger Zone card, so it shows no Leave Team button and no Delete Team button.

Some older RichAPI reference material describes a Leave Team button inside a Danger Zone card on this page. The production dashboard shows no such card. Use the removal procedure above instead.

A removal deletes one record: your membership of the workspace. Nothing else moves.

Credits belong to the organization, not to a member. A departure returns no credit and moves no credit. RichAPI cannot move a credit to your personal account.

CAUTION: Revoke every API key of the workspace that you hold in a script before you leave. A key that you created stays active in the workspace, and every call with that key still spends from the organization balance. At the list price of $0.02 per credit, 1,000 calls on a 1-credit endpoint cost $20.00.

Every RichAPI workspace must keep at least one member with the Owner role. When a team has one Owner, RichAPI blocks two actions.

A second rule protects every Owner. An Owner cannot remove or demote another Owner when that team is the other person's only Owner role in the organization. The API returns 403 with the message You cannot remove another owner of this organization. They must hand over ownership themselves, or a system administrator must do it. A demotion returns the same message with demote.

The dashboard reports a block with a red alert. A removal shows Sorry, we couldn't remove the selected member. A role change shows Sorry, we couldn't update the role of the selected member.

So an Owner cannot leave or step down in the dashboard. If you are an Owner and you want to leave, promote another member to Owner first, and then ask support to remove you. The next sections give the steps.

The RichAPI members table shows no Transfer Ownership action. Ownership moves through the Update Role action, which promotes a second member to Owner.

The dashboard shows Role updated successfully. The Role column on that row now shows Owner.

WARNING: Promote a member to Owner only after you confirm the identity of that person. An Owner can invite and remove members, change roles, and manage the team settings. An Owner also counts as an organization owner, so they can buy credits and set spend limits.

A RichAPI workspace holds more than one Owner at the same time. You cannot step down in the dashboard. The actions menu stays hidden on your own row, and the new Owner cannot demote you while this team is your only Owner role in the organization. To step down, write to [email protected] from the email address on your account. Name the workspace URL and the new Owner. For the permission table behind these rules, read Managing Workspace Members and Permissions.

When you are an Owner and you want to leave, use this order.

WARNING: Complete step 2 before step 3. If the workspace still holds one Owner, RichAPI cannot remove you.

RichAPI closes a workspace as a support request. The dashboard shows no Delete Team button on any page.

WARNING: Save the records that you need before you write. A closure removes the workspace, the API keys, and the usage history. The credit balance belongs to the organization.

If you want to stop the spend but keep the records, revoke the API key of the workspace instead. That procedure is in Creating and Managing API Keys.

Ask an Owner of the workspace to open the Members tab of the Organization page and select Remove from Account on your row. The RichAPI dashboard holds no control that removes your own membership. Your access ends at once, and a new invitation restores it.

No. The Team tab of the settings page at /home/<workspace-url>/settings shows a Team Logo card and a Team Name card only. It shows no Danger Zone card, so it shows no Leave Team button.

Credits belong to the organization, not to a member, so you lose no personal balance. The credit balance stays with the organization after you leave. RichAPI returns 0 credits for a departure and moves 0 credits to your personal account.

Not in the dashboard. Every RichAPI workspace must keep at least one member with the Owner role, and RichAPI blocks the removal with the message Cannot remove the last owner from a team. Promote a second member to Owner first, and then ask [email protected] to remove you.

Open the Members tab of the Organization page, select the actions menu on the row of the member, select Update Role, and select Owner. The members table shows no Transfer Ownership action today. To step down afterwards, write to [email protected]. The new Owner cannot demote you while this team is your only Owner role in the organization.

No. The RichAPI dashboard shows no Delete Team button. Write to [email protected] from the email address of an Owner, and name the workspace URL.

The API key stays with the workspace and keeps working. Every call with that key spends from the organization balance. Ask an Owner to revoke the key before you leave.

No. A departure deletes one membership record. The workspace URL, the workspace name, the logo, the API keys, and the endpoint access of the workspace all stay the same.

Next: Workspace Settings, Themes, and Security