---
title: "Leave an organization"
description: "How to end your own membership in an IoTFlows organization, and what it costs you. The Leave organization row sits near the bottom of Organization Settings at /settings/organization and is there for every member whatever their role. Leave, then Confirm Leave, and IoTFlows reports \"You left <organization> organization\" and returns you to the dashboard home. An Organization Owner has to hand ownership to another member first, because an organization cannot be left without an Owner. Leaving costs you every asset, board, team, and chat scoped to that organization; your IoTFlows account and any other organization you belong to are untouched. There is no way back on your own: rejoining takes a fresh invite, and the new membership starts with access to all machines and no team or board memberships."
category: "Organization settings"
source_url: "https://www.iotflows.com/docs/admin/leave-an-organization/"
---
# Leave an organization

Remove yourself from an organization, and what you lose when you do.

Leaving ends your membership in one organization, and nothing else. The control is the **Leave organization** row in Organization Settings, at `/settings/organization`, and it renders for every member whatever their role.

**Before you start.** If you are the *Organization Owner*, the role that pays for IoTFlows, give another member that role first. See [Transfer ownership](/docs/admin/manage-members/#ownership) and [Owner-only actions](/docs/admin/roles-reference/#owner-only). An organization cannot be left without an Owner.

## Leave
1. Open Organization Settings from the gear icon in the dashboard header, or go to `/settings/organization`.
2. Scroll to the **Leave organization** row, below **Organization description**.
3. Select **Leave**. The row turns into a confirmation reading `Are you sure you want to leave Midwest Tooling organization?`
4. Select **Confirm Leave**.

IoTFlows reports "You left Midwest Tooling organization", drops the organization from your switcher, and returns you to the dashboard home page. To back out before that, select **Cancel**.

![The bottom of the Organization card in Organization Settings, as a member who is not the Owner sees it. The Organization description row reads IoTFlows demonstration plant., and the Leave organization row sits directly below it, with a violet highlight around its Leave button](/images/admin/adm-leave-01.webp)

*Leaving an organization. An Owner must transfer ownership first.*

If the request fails, IoTFlows shows an error toast carrying the message the server sent back, and you are still a member. That toast is what an Owner who has not transferred ownership sees.

> **Warning:**
> **Still in the organization after you left?**
>
> Check the organization switcher. If the organization is still listed, the membership was not removed, and the likeliest reason is that you are the last administrator of something inside it. Ask an administrator to remove you instead: their dialog has [a second step](/docs/admin/manage-members/#last-admin) that settles what you administer, and the **Leave organization** row has none.

## What you lose
Everything scoped to that organization: its assets and reports, its Scheduler and Maintain boards, its teams, and every chat that lives inside it. You keep your account, your profile, and any other organization, see [Switch between organizations](/docs/get-started/switch-organizations/). The full account of what stays behind, including your open work orders, which stay open and become unassigned, is in [What removal does](/docs/admin/manage-members/#after-removal).

Leaving is not the same as being removed by an administrator, but the result for your access is identical. If you might come back, ask an administrator to change your role instead, for example to Organization Observer, which keeps the membership and the settings attached to it. Compare the roles in [What each role can do](/docs/admin/roles-reference/#matrix).

## Rejoining
There is no self-serve way back in. An Owner or Administrator has to [invite you again](/docs/admin/invite-members/), and the invite builds a new membership rather than restoring the old one. Two things do not come with it:

- **Machine access resets to every machine.** Any [restriction](/docs/admin/machine-access/) that was set on your old membership is gone and has to be set again.
- **Team and board memberships are gone.** Someone has to add you back to each one by hand.

## See also
- [Change roles and remove members](/docs/admin/manage-members/)
- [Switch between organizations](/docs/get-started/switch-organizations/)
- [Roles and permissions](/docs/admin/roles-reference/)
- [Invite people to your organization](/docs/admin/invite-members/)
- [Contact IoTFlows](/docs/get-started/get-support/)