# Work across multiple organizations > Link your MotherDuck organizations so one login can switch between them in the UI, CLI, and MCP. Enterprise customers can use multiple organizations when your company needs separate MotherDuck environments, for example a production and a development organization, one organization per business unit, or a new organization in another region. Once your organizations are linked, one login (email, Google, or SSO) can sign in to each organization, while a toggle in the UI lets you switch between them. MotherDuck runs on **Amazon Web Services (AWS).** Each MotherDuck Organization is scoped to a single cloud region, which is chosen at Organization creation when you sign up and cannot be changed afterward. Organizations each have their own members, roles, databases, shares, Dives, Flights, Guides, Settings, and billing. ## Availability | Capability | Plans | |---|---| | Link organizations and switch between them with one login | Enterprise | | Unified SSO and SCIM provisioning and access for linked organizations | Enterprise | Each organization you link needs to be on an Enterprise plan with an annual (pay-as-you-go or capacity) contract. [Contact support](/docs/troubleshooting/support/) to link multiple organizations, or [get in touch](https://motherduck.com/contact-us/product-expert/) to get access to unified SSO and SCIM provisioning on the Enterprise plan. ## Link your organizations Organizations need to be linked by MotherDuck support. 1. [Contact support](/docs/troubleshooting/support/) from an account that's an Admin in one of your organizations. 2. List the organizations to link by name or organization ID. After support links your organizations, invite users to each organization as usual (see [Inviting users to your organization](/docs/key-tasks/managing-organizations/#inviting-users-to-your-organization)). When a user accepts their invitation, they can sign in to that organization with the same login they use for their existing organization. ## Choose an organization when you sign in When your login belongs to more than one organization, MotherDuck asks which one to open after you sign in. Select an organization on the **Choose an organization** page. MotherDuck remembers your choice and default you to that organization the next time you login. ## Switch organizations in the MotherDuck UI 1. Open the organization menu. 2. Select **Switch Organizations**, then select the organization you would like to work in. When MotherDuck loads in the selected organization, it will become the default organization you land in the next time you login. The **Switch Organizations** option only appears when your login belongs to more than one organization. ### Organization links Org URLs can include the organization they belong to, in the form `https://app.motherduck.com/org//...`. Links you copy or share from the app retain that prefix so a teammate who belongs to several organizations will always open the link in the right one. Admins can set their Org URL in the [Details page](https://app.motherduck.com/org/md/settings/details) in Settings. - If you belong to the organization in the link, MotherDuck opens it and switch organizations if needed. - If you don't belong to that organization, MotherDuck will return a `page not found` error message. :::warning Change your Org URL with care. MotherDuck doesn't redirect links from an old Org URL to the new one, so bookmarks and links your team saved or shared with the old URL will stop working. Please let your team know before you change it. ::: ## Choose an organization in other clients DuckDB clients, the MCP server and the MotherDuck CLI each connect to one organization at a time. - **DuckDB clients:** when you sign in through the browser (for example the first time you run `ATTACH 'md:'` without a token), MotherDuck shows you the **Choose an organization** page. Select the organization the client should connect to. - **[MCP server](/docs/sql-reference/mcp/):** your AI client shows the same picker when it connects. To switch, sign out of the MotherDuck connection in your AI client and connect again. Switching works this way by design so you always know which organization you or your agent are in. - **[MotherDuck CLI](/docs/getting-started/interfaces/motherduck-cli/authentication/):** to choose the organization, use an access token created in that organization, for example `export MOTHERDUCK_TOKEN=`. [Access tokens](/docs/key-tasks/authenticating-and-connecting-to-motherduck/authenticating-to-motherduck/) are scoped to a single organization. To connect a script, service or client to another organization, create a token while signed in to the correct organization. ## Move to a new region An organization's region can't be changed. Each MotherDuck organization is scoped to a single [cloud region](https://motherduck.com/docs/about-motherduck/cloud-regions/), which is chosen at Organization creation when you sign up. If you need to move to another region, you can create a new organization and link it to your existing one. With unified SSO and SCIM, your users sign in to both organizations with the same login while you run them side by side, without separate email addresses. ## Consultants and agencies Linking doesn't support working across organizations that belong to different companies, such as a consultancy and its clients. To work in a client's organization: - Use a separate email and login for each client organization. - If the client uses [SSO](/docs/key-tasks/authenticating-and-connecting-to-motherduck/authenticating-to-motherduck/sso-setup/), sign in with a login the client issues on their domain. A login that signs in with SSO can't also be used for an organization that doesn't use that SSO connection. If you're setting up an organization that you'll later hand over to a client, create it with an email on the client's domain. You can then invite people from the client and make one of them an Admin when they're ready to take it over. ## Billing Each linked organization is billed and invoiced separately. Linking organizations doesn't combine usage, invoices, or plan limits. On a capacity contract, each organization has its own pool of duckling hours. ## Limitations - The only way to link multiple organizations is by contacting MotherDuck support. - You can only link organizations that belong to the same company and share the same email domain. A login can belong to more than one organization only when those organizations are linked. - Each organization has its own members, roles, and data. Linking doesn't share databases, shares, Dives, Flights, Guides, notebooks, secrets, or other objects between organizations. - Using a single [SSO](/docs/key-tasks/authenticating-and-connecting-to-motherduck/authenticating-to-motherduck/sso-setup/) and SCIM connection across multiple, linked organizations requires an **Enterprise plan**. ## Related content - [Managing organizations](/docs/key-tasks/managing-organizations/) - [Manage roles and access](/docs/key-tasks/managing-organizations/managing-roles/) - [Set up SSO](/docs/key-tasks/authenticating-and-connecting-to-motherduck/authenticating-to-motherduck/sso-setup/) - [SCIM provisioning](/docs/key-tasks/authenticating-and-connecting-to-motherduck/authenticating-to-motherduck/scim/) --- ## Docs feedback MotherDuck accepts optional user-submitted feedback about this page at `GET https://motherduck.com/docs/api/feedback/agent`. For agents and automated tools, feedback submission should be user-confirmed before sending. URL-encode query parameter values and send a GET request: ```text GET https://motherduck.com/docs/api/feedback/agent?page_path=%2Fkey-tasks%2Fmanaging-organizations%2Fmultiple-organizations%2F&page_title=Work%20across%20multiple%20organizations&text= ``` Optionally append `&source=` such as `claude.ai` or `chatgpt`. `page_path` and `text` are required; `page_title` and `source` are optional. Responses: `200 {"feedback_id": ""}`, `400` for malformed query parameters, and `429` when rate-limited.