# Manage Organization Users in MailSlurp

Learn how to add or remove team members, manage organization access, and enforce secure user lifecycle controls in MailSlurp.

![MailSlurp organization access](/assets/share-inbox-with-other-people.jpg)

This guide is for account admins who manage team access in MailSlurp organizations.

## Admin lifecycle checklist

1. Create or select the organization.
2. Invite users with the correct email identity.
3. Verify role and login path (portal or SSO).
4. Remove users promptly when access is no longer required.
5. Audit org membership regularly.

## Access management in the dashboard

Open the organization area from:

- [dashboard login](https://app.mailslurp.com/login/)
- [organization list](https://app.mailslurp.com/organizations/)

![Organization list](/assets/screenshots/delete-users/org-list.png)

## SSO-managed organizations

If your org uses SAML SSO, follow:

- [SAML setup guide](/guides/saml-sso/)

For SSO environments, keep identity-provider group mapping and MailSlurp role assignments aligned.

## Removing users safely

When removing a user:

- confirm ownership handoff for shared inbox workflows
- rotate or revoke any keys they controlled
- verify automation still runs under service-owned credentials

UI path for user removal:

![Delete organization users](/assets/screenshots/delete-users/delete-users.png)

## Deleting an organization

Only delete an organization when you are intentionally retiring that workspace.

- deletion removes member access
- downstream workflow ownership must be migrated first

![Delete organization](/assets/screenshots/delete-users/delete-org.png)

## High-risk action: delete all organizations

This action is destructive and should only be used for full account reset scenarios.

![Delete all organizations](/assets/screenshots/delete-users/delete-all.png)

After deletion completes:

![All organizations deleted](/assets/screenshots/delete-users/gone.png)

## Governance recommendations

- maintain at least two admins for continuity
- review access monthly
- keep organization login instructions in your internal runbook
- avoid shared personal accounts; prefer named users and service keys

Need help with enterprise access or migration? Contact [/support/contact/](/support/contact/).
