---
site: steel.dev
collection: docs
canonical_url: https://steel.dev/docs/account/organizations-and-members
markdown_url: https://steel.dev/docs/account/organizations-and-members.md
content_signal: ai-input=yes, ai-train=yes, search=yes
title: Organizations and members
description: Invite teammates to your organization, manage seats, require two-step verification, and set up SSO on Enterprise.
summary: Invite teammates to your organization, manage seats, require two-step verification, and set up SSO on Enterprise.
type: how-to
reviewed: 2026-11-12
prerequisites: []
related:
  - https://steel.dev/docs/account/api-keys.md
  - https://steel.dev/docs/account/projects.md
agent_setup: https://setup.steel.dev/install.md
docs_index: https://steel.dev/docs/sitemap.md
---

# Organizations and members

An organization is your Steel account. It holds your projects, API keys, plan, credits and limits, and its members sign in to the dashboard to work in it. Add members so that your team shares one plan and one bill. One person can belong to more than one organization. The [MCP server](https://steel.dev/docs/control/mcp-server), for example, asks which organization to use when you sign in.

Launch includes up to 3 seats, and Scale and Enterprise include unlimited seats. See [Pricing](https://steel.dev/docs/platform/pricing).

Each member has a role, which the dashboard shows as **Admin** or **Member**. An admin has full access to settings and billing. A member can use the organization and its projects. The dashboard can also show **Owner** for the person who created the organization. An owner can do everything that an admin can, and the dashboard cannot change an owner's role. The role decides who can do these tasks:

| Task | Who can do it |
| - | - |
| Create a project key | Any member |
| Create or rotate an organization key | Admins |
| Create, change or delete a project | Admins |
| Change the plan, buy credits, set auto top-up and see invoices | Admins |

## Invite a member

1. In the [dashboard](https://app.steel.dev/settings/organization), open **Manage Organization** in the sidebar.
2. Under **Members**, click **Invite member**.
3. Under **Email addresses**, type an address and press Enter. Add more addresses the same way.
4. Under **Role**, choose **Member** or **Admin**.
5. Click **Send invite**.

Steel emails each person an invitation, which is valid for 2 days. Until the person accepts it, the invitation is under **Invited members**. To cancel it, open the menu at the end of its row and click **Revoke invite**.

Launch includes up to 3 seats. For more members, change the plan to Scale in [Billing and usage](https://steel.dev/docs/platform/billing-and-usage).

## Remove a member

1. In the dashboard, open **Manage Organization** in the sidebar.
2. Under **Members**, find the member in **Current members**.
3. Open the menu at the end of the row, and click **Remove member**.
4. Click **Yes, remove**.

The member loses access to the organization. You can invite them again later. To change a role instead, click **Change role** in the same menu.

API keys belong to the organization, not to the member who created them. Removing a member does not revoke the API keys that they created. The dashboard does not show who created a key, so [rotate](https://steel.dev/docs/account/api-keys#rotate-a-key) each key that the member used.

## Require two-step verification

An organization can require its members to sign in with two-step verification. A member of such an organization must set up two-step verification before they can sign in to the MCP server.

Each member sets up two-step verification for their own account, with an authenticator app:

1. Click your name at the bottom of the sidebar, then **Manage account**, then **Security** ([direct link](https://app.steel.dev/settings/profile#/security)).
2. Under **Two-factor authentication**, click **Connect app**.
3. Scan the QR code with your authenticator app, and click **Continue**.
4. Enter the 6-digit code from the app, and click **Continue**.
5. Save the backup codes that Steel shows, for when you lose access to the app. Each code works once.

To require two-step verification for every member, an admin first sets it up for their own account, and then follows these steps:

1. Open **Manage Organization** in the sidebar.
2. Under **Require two-step verification**, click **Require for everyone**.
3. Enter a code from your authenticator app or a backup code, and click **Require**.

Members without an authenticator app lose access at their next sign-in refresh, and Steel asks them to set one up to continue. To turn the requirement off, click **Stop requiring**.

## Set up SSO

Enterprise SSO lets your members sign in through your own identity provider, over SAML or OIDC. It is available on Enterprise only. Steel sets up the connection for you. The dashboard has no screen for it. To start, [contact sales](https://steel.dev/enterprise).

After Steel connects your identity provider and verifies your email domain, your members enter their work email on the sign-in page and click **Sign in with SSO**. A person who signs in this way for the first time joins your organization as a member. If your identity provider sends a role that you asked Steel to map to admin, the person joins as an admin.

## Check that it worked

Open **Manage Organization**. Each person that you invited is under **Invited members** until they accept, and then under **Current members**, with the role that you chose. A member that you removed is no longer under **Current members**. When the organization requires two-step verification, the button under **Require two-step verification** is **Stop requiring**.

## Next steps

- [Security and compliance](https://steel.dev/docs/platform/security-and-compliance): See how Steel isolates sessions and encrypts the credentials that you store.
