MailSlurp organizations let teams collaborate in one managed workspace with shared access controls.

## When to use organizations

Use organizations when you need:

- shared access to inbox and testing workflows
- controlled onboarding/offboarding for teammates
- centralized identity with SAML or OIDC SSO
- cleaner separation between personal and team usage

## Prerequisites

- plan with organization support
- admin user responsible for membership lifecycle
- defined login policy (passwordless, password, or SSO)

## Step-by-step setup

### 1) Create an organization

Sign in to [app.mailslurp.com](https://app.mailslurp.com/login/) and open the organizations area.

![Create organization](/assets/screenshots/enterprise/team-new.png)

Choose an organization slug carefully. It becomes part of your team login URL.

![Organization details](/assets/screenshots/enterprise/team-new-filled.png)

### 2) Invite team members

Add users by email from the organization page.

![Invite users](/assets/screenshots/enterprise/invite-user.png)

Users receive an invite flow and should authenticate through the organization route.

![User added](/assets/screenshots/enterprise/user-added.png)

### 3) Share the correct login portal

Organization users should sign in via the organization-specific entry path, not the generic personal portal.

![Organization login](/assets/screenshots/enterprise/org-login.png)

### 4) Verify successful team access

After login, users should see organization context in their dashboard.

![Organization dashboard](/assets/screenshots/enterprise/dashboard.png)

## Optional: enable enterprise SSO

For enterprise identity governance, configure SAML or OIDC:

- [SAML SSO organization guide](/guides/saml-sso/)
- [OIDC SSO setup](/docs/oidc/)
- [Microsoft Entra OIDC and SCIM environment guide](/guides/entra-oidc-scim-setup/)
- [Okta OIDC and SCIM environment guide](/guides/okta-environments-setup/)

Use SSO when you need lifecycle automation tied to your identity provider, or when users should land in assigned MailSlurp environments from an identity provider app tile.

## Operational best practices

- keep at least two organization admins
- review membership monthly
- remove users immediately after role changes
- avoid shared credentials; use named accounts and scoped keys
- use [organization governance and quotas](/docs/governance/) to review seats, usage, tags, quota events, and API key consumption
- use [notifications](/docs/notifications/) to route account, billing, quota, and render alerts to connected channels

## Related guides

- [Enterprise reporting and quota management](/guides/enterprise-reporting-and-quotas-guide/)
- [Organization governance and quotas](/docs/governance/)
- [Notifications and Slack integrations](/docs/notifications/)
- [Manage organization users](/support/managing-organization-users/)
- [Sign-in troubleshooting](/support/password-sign-in-errors/)
- [Account setup guide](/guides/signing-up/)