> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lovable.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Organizations: manage several Enterprise workspaces together

> Group your company's Lovable workspaces under one organization: set up SSO and SCIM once, see every member and role in one place, and publish apps company-wide.

> [!NOTE]
>
> Lovable sets up organizations on request. Your account team creates your organization and adds your workspaces to it. See [Set up an organization with your account team](#set-up-an-organization-with-your-account-team).

An **organization** groups several Lovable workspaces under one company. The company sets up [SSO](https://docs.lovable.dev/features/organization-identity.md#set-up-sso-for-the-organization) with its identity provider, such as Okta or Microsoft Entra ID, one time, and that setup covers every workspace in the organization. With [SCIM](https://docs.lovable.dev/features/organization-identity.md#provision-members-with-scim), the identity provider also adds and removes members automatically.

Org admins, the people who manage the organization, see every member and role in one place. Members can publish internal apps to everyone in the company. Each workspace keeps its own projects, members, groups, and billing.

* **Available on:** Enterprise plans
* **Access:** Org admins
* **Location:** [Organization settings](https://lovable.dev/organization) (**workspace switcher → Organization settings**)

> [!NOTE]
>
> This page is about organizations, where you manage several workspaces together. Looking for a way to separate teams inside one workspace? See [Groups](https://docs.lovable.dev/features/groups.md) and [Project folders](https://docs.lovable.dev/introduction/project-folders.md). These are different features.

## When to use an organization

Use an organization when several of your company's Lovable workspaces, for example one per team, region, or business unit, need the same identity rules.

Without an organization, every workspace verifies its own domains, connects its own SSO provider, and runs its own SCIM connection. A workspace admin who changes a setting in one workspace changes it in that workspace only, so the workspaces end up with different rules.

An organization also lets a team in one workspace publish an internal app to the organization. Colleagues in every other workspace can then open it, and people outside the organization cannot.

## Set up an organization with your account team

Ask your account team, the people you work with on your Enterprise contract, to create an organization for your company.

Org admins cannot create an organization, or a workspace inside one, from organization settings. Your account team creates the organization and its workspaces with you.

An org admin can add an existing workspace by [claiming it](#claim-a-workspace-whose-primary-owner-uses-a-verified-domain). Claiming works when the workspace's [primary owner](https://docs.lovable.dev/features/people.md#the-primary-owner), the owner Lovable uses for billing, has an email address on one of the organization's verified domains.

Your account team:

* Creates the organization and adds your workspaces to it.
* Decides with you how each workspace joins, including whether it becomes **Managed by the organization**. See [What happens when a workspace joins](#what-happens-when-a-workspace-joins).
* Adds a workspace to another organization after an org admin removes it from this one.
* Deletes a workspace on the Enterprise plan when you ask. See [Delete a workspace](https://docs.lovable.dev/introduction/delete-workspace.md).

After your organization exists, an org admin manages its workspaces, people, and identity settings without your account team. See [Open organization settings](#open-organization-settings).

## What the organization manages and what each workspace keeps

The organization manages the identity setup that its workspaces share:

* **Verified domains**, so the company proves it owns its email domains once. See [Verify a domain for the organization](https://docs.lovable.dev/features/organization-identity.md#verify-a-domain-for-the-organization).
* **SSO providers**, and the optional **Enforce SSO for org admins** setting, which requires org admins to log in through SSO. See [Set up SSO for the organization](https://docs.lovable.dev/features/organization-identity.md#set-up-sso-for-the-organization).
* **SCIM provisioning** and **provisioning groups**. Provisioning adds and removes members automatically. Provisioning groups decide which workspace a person joins and with which role. See [Provision members with SCIM](https://docs.lovable.dev/features/organization-identity.md#provision-members-with-scim).
* **Org admins**, the people who manage the organization. See [Who can manage the organization](#who-can-manage-the-organization).
* **Audit logs** for organization-level actions and for the events of every workspace in the organization. See [Review activity across the organization](#review-activity-across-the-organization).

Each workspace keeps:

* **Projects, folders, groups, and connectors**.
* **Members and their workspace roles**. Someone can belong to several workspaces in the organization, with a different role in each.
* **Plan, credits, invoices, and usage limits**. The organization has no shared credit pool.
* **Identity and security settings**, such as **Enforce SSO**, how long an SSO session lasts, and who joins the workspace automatically. These settings decide how the organization's identity setup applies to the workspace. The workspace also keeps everything on its **Privacy & security** tab. See [Set identity per workspace](https://docs.lovable.dev/features/organization-identity.md#set-identity-per-workspace).

Both org admins and the workspace's admins and owners can change a workspace's identity and security settings. When an org admin sets the workspace to **Managed by the organization**, only org admins can change them. See [Lock workspace settings to the organization](https://docs.lovable.dev/features/organization-identity.md#lock-workspace-settings-to-the-organization).

## What happens when a workspace joins

A workspace joins an organization when your account team adds it or when an org admin [claims it](#claim-a-workspace-whose-primary-owner-uses-a-verified-domain). A workspace belongs to at most one organization. Publishing to the organization, the [SSO session shared across workspaces](https://docs.lovable.dev/features/organization-identity.md#set-up-sso-for-the-organization), and SCIM apply only to the organization's Enterprise workspaces.

A claimed workspace gets a new primary owner, chosen by the org admin, and becomes **Managed by the organization**. The rest of this section covers workspaces your account team adds.

A workspace your account team adds keeps its projects, members, roles, plan, and credits. Members keep their access and keep logging in the same way. The workspace also keeps its own verified domains and SSO provider, and the organization's verified domains and SSO provider cover it as well. See [Set up SSO for the organization](https://docs.lovable.dev/features/organization-identity.md#set-up-sso-for-the-organization).

Decide with your account team whether the workspace joins as **Managed by the organization**:

* **Managed by the organization**: only org admins can change the workspace's identity and security settings. Lovable removes the workspace's own SCIM connection, disables **Verified email sign-up** for it, and enables **SSO JIT** (just-in-time provisioning) if it was disabled.
* **Not managed**: the workspace keeps its SCIM connection, **Verified email sign-up**, and **SSO JIT** settings, and its admins and owners can still change them.

Your account team can create the organization from one of your workspaces. Your account team can then move that workspace's verified domains, SSO providers, provisioning groups, and SCIM connection to the organization. The SCIM connection keeps working from the organization, and the workspace becomes **Managed by the organization**.

An org admin can transfer a workspace's own verified domains and SSO providers to the organization at any time after it joins. See [Transfer workspace identity to the organization](https://docs.lovable.dev/features/organization-identity.md#transfer-workspace-identity-to-the-organization).

An org admin can change **Managed by the organization** for any workspace at any time, whichever way that workspace joined. See [Lock workspace settings to the organization](https://docs.lovable.dev/features/organization-identity.md#lock-workspace-settings-to-the-organization).

After the workspace joins, the organization adds people to it through the organization's SSO provider, through SCIM, or through **Verified email sign-up**. A workspace that kept its own SSO provider also adds people through that provider. An org admin enables **SSO JIT** and **Verified email sign-up** for a workspace in organization settings. See [Set identity per workspace](https://docs.lovable.dev/features/organization-identity.md#set-identity-per-workspace).

## What changes for members of a workspace

When your workspace belongs to an organization, three things change for you:

* The **workspace switcher**, the menu under your workspace name on the dashboard, groups the workspaces you belong to under the organization's name. The switcher lists workspaces outside the organization under **Other workspaces**. The grouping changes nothing about your access.
* If your workspace is **Managed by the organization**, only org admins can change its **Identity** and **Privacy & security** settings. The **Identity** tab in workspace settings shows that the organization manages it. Ask an org admin for changes.
* The publish dialog shows an option named after your organization. When you choose it, members of every workspace in the organization can open the app after logging in. No one outside the organization can open an app published this way. See [Publish to your organization](https://docs.lovable.dev/features/website-access.md#publish-to-your-organization).

Your projects, members, groups, plan, credits, and the way you log in do not change when your workspace joins an organization. Joining can change one thing: how people join your workspace automatically, such as through SSO or SCIM. See [What happens when a workspace joins](#what-happens-when-a-workspace-joins).

## Who can manage the organization

An organization has two roles.

| Role | What they can do |
| :- | :- |
| **Admin** (org admin) | Open **Organization settings**. Manage the workspaces, people, identity settings, and [other org admins](https://docs.lovable.dev/features/organization-people.md#make-someone-an-org-admin) of the organization. |
| **Member** | Everyone else in the organization's workspaces. They work in the workspaces they belong to and do not see **Organization settings**. |

Being an org admin does not add you to the organization's workspaces, so you do not see the projects in them.

## Open organization settings

Org admins open **Organization settings** from the **workspace switcher**. If you are an org admin of several organizations, select one from the list.

The settings sidebar lists its pages in three groups:

* **Organization**: a page named after your organization, where you set its name and avatar. A second page, [Workspaces](#review-and-remove-workspaces), lists the organization's workspaces, and from there you can [claim workspaces outside the organization](#claim-a-workspace-whose-primary-owner-uses-a-verified-domain).
* **Access**: [People](https://docs.lovable.dev/features/organization-people.md) shows everyone across the workspaces. [Identity](https://docs.lovable.dev/features/organization-identity.md) is where you set up domains, SSO, and SCIM.
* **Security**: [Audit logs](#review-activity-across-the-organization) shows activity across the organization.

## Review and remove workspaces

The **Workspaces** page in organization settings lists every workspace in the organization. Search by workspace name to find one. Each row shows:

* Plan
* Members
* Credit usage
* Workspace admins

From a workspace's row you can:

* Select **Add members** to [add people to that workspace](https://docs.lovable.dev/features/organization-people.md#add-someone-to-a-workspace). The action is disabled when your identity provider manages the workspace's members through SCIM.
* Select **View workspace settings** to review and change that workspace's privacy and security settings, including its publishing and sharing policies.
* Select **Remove** to take the workspace out of the organization, then confirm. You cannot remove the last workspace in an organization.

Removing a workspace does not delete it. Its members keep their workspace roles. The organization's provisioning groups and verified domains stop adding people to the workspace.

If the workspace was the organization's **Default workspace** for SCIM provisioning, Lovable clears the default. Set a new **Default workspace** under **Provisioning** on the organization's [Identity](https://docs.lovable.dev/features/organization-identity.md#provision-members-with-scim) page.

Deleting a workspace on the Enterprise plan goes through your account team, whether or not the workspace is in an organization. See [Delete a workspace](https://docs.lovable.dev/introduction/delete-workspace.md).

## Claim a workspace whose primary owner uses a verified domain

Org admins can claim a workspace whose [primary owner](https://docs.lovable.dev/features/people.md#the-primary-owner) uses an email address on one of the organization's [verified domains](https://docs.lovable.dev/features/organization-identity.md#verify-a-domain-for-the-organization). Claiming brings in workspaces that people at the company created outside any organization, such as a team's own workspace.

The workspace joins the organization 14 days after Lovable notifies its primary owner. A claimed workspace can be on any plan, and it keeps its plan and billing. On a plan other than Enterprise, it does not get the organization features that [apply only to Enterprise workspaces](#what-happens-when-a-workspace-joins).

To claim workspaces:

1. In [Organization settings](https://lovable.dev/organization), open **Workspaces** and click **Claim workspace**. The **Claim workspaces** page opens, and its **Available workspaces** tab lists the workspaces you can claim.
2. Select the workspaces. To check your selection, click **Review selected**.
3. In the bar that shows how many workspaces you selected, click **Claim workspace**. A dialog opens.
4. In **New primary owner**, choose who becomes the primary owner of the workspaces: an org admin or a member of a workspace already in the organization.
5. Click **Schedule claim**.

Lovable notifies the primary owner of each workspace in their **Inbox**, by email, and with a banner in Lovable. No one else in the workspace is notified. The notice links to a review page, where the primary owner can:

* Move personal projects to a personal workspace before this workspace joins, so they stay out of the organization. See [Move a project to another workspace](https://docs.lovable.dev/features/projects/settings.md#move-a-project-to-another-workspace).
* Select **Change primary owner** to [transfer primary ownership](https://docs.lovable.dev/features/people.md#transfer-primary-ownership) to another account, such as their personal Lovable account. Any transfer of primary ownership before the workspace joins ends the claim, and the workspace stays out of the organization.
* Select **Approve now** to join the organization without waiting for the 14 days.

If the primary owner does nothing, the workspace still joins when the 14 days are over.

When the workspace joins, the person you chose in **New primary owner** becomes its primary owner. The previous primary owner stays in the workspace as an owner, and any other owners keep their role.

The joined workspace also becomes **Managed by the organization** and takes the settings the organization manages.

Lovable removes the workspace's own SCIM connection and disables **Verified email sign-up** for it. If **SSO JIT** (just-in-time provisioning) was disabled for the workspace, Lovable enables it, so SSO adds people to the workspace until an org admin disables it again. See [Set identity per workspace](https://docs.lovable.dev/features/organization-identity.md#set-identity-per-workspace).

The **Claim history** tab shows the status of each claim. When a claim fails or is no longer eligible, the tab also shows the reason. Reasons include that the workspace has no seat left for the new primary owner, or that its primary owner changed.

When a claim ends, Lovable notifies the previous primary owner, the new primary owner, and the org admin who scheduled the claim in their **Inbox**.

To stop a claim while its status is **Sending notice** or **Scheduled**, open the claim's menu in **Claim history** and select **Cancel claim**. A new claim on the same workspace starts a new 14-day notice.

## Review activity across the organization

The **Audit logs** page in organization settings shows organization-level actions. These include a workspace added or removed, a verified domain or SSO provider changed, and a person's organization role changed. The page also shows the audit events of every workspace in the organization.

Filter by workspace to review one workspace's events. Export the logs the same way as on the workspace [audit logs](https://docs.lovable.dev/features/audit-logs.md) page.

## Limitations

An organization is an administration layer over your workspaces, not a merged workspace. These limits follow from that:

* The organization has no shared credit pool, and billing stays with each workspace.
* The organization has no shared **Privacy & security** settings. Each workspace has its own.
* You cannot create a workspace inside the organization from organization settings. Your account team creates workspaces and adds existing ones. An org admin can also add an existing workspace by [claiming it](#claim-a-workspace-whose-primary-owner-uses-a-verified-domain), when its primary owner uses one of the organization's verified domains.
* Organizations have one level. An organization cannot belong to another organization.
* An organization lets you publish an app to people in other workspaces. It does not let people in different workspaces edit the same project. To work on a project together, people need access in the workspace that owns it, as members or as [external collaborators](https://docs.lovable.dev/features/people.md#external-collaborators).

## FAQ

> [accordion] Can an org admin see the projects in my workspace?
>
> Only if they are a member of your workspace. The org admin role manages identity, people, and workspaces, and does not include access to the projects inside them. An org admin can add themselves to a workspace from the organization's [People page](https://docs.lovable.dev/features/organization-people.md#add-someone-to-a-workspace). They cannot do this in a workspace managed by SCIM, where your identity provider adds the members.

> [accordion] Does joining an organization change my workspace's billing?
>
> No. Your workspace keeps its plan, credits, invoices, and usage limits. For contract questions, contact your account team. See [What the organization manages and what each workspace keeps](#what-the-organization-manages-and-what-each-workspace-keeps).

> [accordion] Can a workspace belong to two organizations?
>
> No. A workspace belongs to at most one organization. To move a workspace to another organization, an org admin removes it from the first one, and your account team adds it to the other. See [What happens when a workspace joins](#what-happens-when-a-workspace-joins).

> [accordion] Can an org admin delete a workspace?
>
> No. Org admins can remove a workspace from the organization, which keeps the workspace and its members. Deleting an Enterprise workspace goes through your account team. See [Review and remove workspaces](#review-and-remove-workspaces).

> [accordion] What happens to my workspace's SSO when it joins an organization?
>
> Members keep logging in the same way. The workspace keeps its own SSO provider and verified domains. Your account team moves them only for the workspace the organization was created from, and an org admin can transfer them later. See [What happens when a workspace joins](#what-happens-when-a-workspace-joins).
