> ## 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.

# Control who can visit your published app

> Choose who can visit your published app, invite people outside your workspace, and approve access requests. Website access is separate from project access.

Website access controls who can visit your published app at its live URL. On every plan you can leave the app open to anyone with the link, or name the people who may open it.

Business and Enterprise plans add your whole workspace and [groups](https://docs.lovable.dev/features/groups.md). An Enterprise workspace in an [organization](https://docs.lovable.dev/features/organizations) can open the app to everyone in the organization. An Enterprise workspace can also open it to everyone with a verified email at one of its [verified domains](https://docs.lovable.dev/features/verified-domains.md).

This page covers choosing the audience, inviting people outside your workspace, removing someone's access, and answering requests from people who have no access. To get an app live in the first place, see [Publish your Lovable project](https://docs.lovable.dev/features/publish.md).

> [!NOTE]
>
> **Project access vs published website access (important difference)**
>
> Lovable uses two independent access settings:
>
> * **Project access (editor access)** controls who can view and edit your project in the editor, including your source code, project chat history, work-in-progress, and any changes that have not been published yet.
> * **Website access (published URL access)** controls who can visit the published app at its live URL.
>
> These settings are independent. Publishing does not change who can access your project in the editor, and changing project access does not affect who can visit the published app.

To change who can open the project in the editor, see [Control project access](https://docs.lovable.dev/features/project-visibility.md).

## Who can see your published app

In your project, click **Publish** to open the publish dialog, then select the visibility row below the website address. The row opens the **Who can view your site?** picker, where you choose who can visit your published app. The options you get depend on your plan.

When you select **Publish** (or **Publish changes** on a published project), Lovable updates who has access and sends any invite emails.

### Free and Pro plans

The picker shows three rows:

* **Public**: Anyone with the URL can visit your published app. This is the default.
* **Workspace**: Not available on your plan. Publishing to your whole workspace or to [groups](https://docs.lovable.dev/features/groups.md) requires a Business or Enterprise plan.
* **Invite only**: Only people you add can visit the published app, after logging in to Lovable. Add workspace members by name, or invite people outside your workspace by email. You can invite up to 10 people per project. See [Invite people outside your workspace](#invite-people-outside-your-workspace).

The project owner, workspace owners, and people the project is shared with directly can always open an invite-only site.

### Business and Enterprise plans

The picker shows these rows, and the organization row only on an Enterprise workspace in an organization:

* **Public** (external publishing): Anyone with the URL can visit your published app.
* Your organization, shown with the organization's name: Members of every workspace in the organization can visit the published app after logging in. See [Publish to your organization](#publish-to-your-organization).
* **Workspace** (internal publishing, shown with your workspace name): Only workspace members can visit the published app after logging in.
* **Custom**: You compose the exact audience: the whole workspace, [groups](https://docs.lovable.dev/features/groups.md), individual members, and people outside your workspace invited by email. An Enterprise workspace in an organization can add people in the organization as well. Any Enterprise workspace can also add an email domain. See [Invite people outside your workspace](#invite-people-outside-your-workspace) and [Publish to an email domain](#publish-to-an-email-domain).

**Custom** is what Free and Pro plans call **Invite only**, with more you can add to it.

With these options you can:

* Build and share internal apps that stay private to your workspace
* Show a private app to a client or contractor without adding them to your workspace
* Share an app with colleagues in other workspaces of your organization

Workspace admins and owners can also set the default audience for all published projects with **Default published app access** in [Workspace settings → Security → Privacy & security → Publishing](https://lovable.dev/settings/privacy-security#publishing).

You can override the workspace default for individual projects in the publish dialog by choosing who can see the website. If unchanged, the project inherits the workspace default.

## Publish to your organization

When your Enterprise workspace belongs to an [organization](https://docs.lovable.dev/features/organizations), you can publish an app to everyone in the organization. Colleagues in other workspaces of your company can then open it, and the app stays private.

To publish to the organization:

1. In your project, click **Publish**.
2. Select the visibility row to open **Who can view your site?**.
3. Choose the option named after your organization.
4. Select **Publish** (or **Publish changes** on a published project). When the dialog confirms **Your website is live**, members of every workspace in the organization can open the app after logging in to Lovable.

External collaborators and people outside the organization cannot open the app through the organization option. A colleague who has never joined a workspace in the organization must join one first, for example by invitation or through the organization's [SSO](https://docs.lovable.dev/features/business/sso.md). Viewing the app does not give anyone access to the project itself.

Visitors log in to Lovable to open the app. A visitor who has no access can [request it](#approve-requests-to-use-your-published-app).

To give one colleague from another workspace access without publishing to the whole organization, choose **Custom** and search for them by name or email. You add them this way rather than with an email invitation, which is for people outside the organization. The picker shows only people who already belong to a workspace in the organization.

To give access to the organization and to specific people, for example a client outside the company, choose **Custom** and add both. The **Custom** card then includes the organization in its summary of who has access.

The option appears only on the Enterprise plan, and only when your workspace belongs to an organization. If both are true and you still do not see it, Lovable has set a publishing policy that does not allow publishing to the organization. Contact your account team.

## Publish to an email domain

On the Enterprise plan, you can publish an app to everyone whose Lovable account uses a verified email at one of your company's [verified domains](https://docs.lovable.dev/features/verified-domains.md), such as `yourdomain.com`. People at the domain can open the app without belonging to your workspace or organization. An address at a subdomain, such as `name@app.yourdomain.com`, does not count.

To publish to an email domain:

1. In your project, click **Publish**.
2. Select the visibility row to open **Who can view your site?**.
3. Select the **Custom** card, then select **View and edit**.
4. Type the domain, such as `yourdomain.com`, in the search field, or pick it from the list. The domain appears as one row that covers everyone at the domain.
5. Select **Done**, then **Publish** (or **Publish changes** on a published project). Everyone at the domain can then open the app after logging in to Lovable.

Lovable sends no email when you add a domain, so send the people at the domain the app's URL yourself. Viewing the app does not give anyone access to the project itself.

The picker lists the domains verified by your workspace and by its organization. The email domain option does not appear when workspace admins and owners set [External viewer invites](https://docs.lovable.dev/features/privacy-and-security-settings.md#external-viewer-invites) to **Off**. Lovable can also hide the option with a publishing policy that does not allow publishing to the organization. To change that policy, contact your account team.

Domains already in the audience keep giving access when admins and owners set **External viewer invites** to **Off**. A domain stops giving access when neither your workspace nor its organization verifies it, or when a publishing policy blocks publishing to the organization.

## Invite people outside your workspace

You can give people outside your workspace, for example a client or a contractor, access to an app that is not public. They do not join your workspace. Project editors and above can manage the website audience.

**1. Open the audience picker**

In the publish dialog, select the visibility row to open **Who can view your site?**. Select the **Invite only** card (Free and Pro plans) or the **Custom** card (Business and Enterprise plans), then select **View and edit**.

**2. Invite by email**

Type the person's email address in the search field. For an address outside your workspace, an **Invite** option appears. Select it to add the person. They appear in the list under the search field, and the card shows who has access.

If the workspace has set [External viewer invites](https://docs.lovable.dev/features/privacy-and-security-settings.md#external-viewer-invites) to **Off**, the email option doesn't appear. If the workspace limits invites to specific email domains, addresses on other domains can't be added, and the picker says the domain isn't allowed.

**3. Apply your changes**

Select **Done** to close the picker. Lovable does not apply the invites or send emails yet. Confirm your changes in the dialog, and Lovable sends each invited person an email and updates who has access.

The invite email contains a link to your site. If the invited person already uses Lovable, they also get an in-app notification. To open the site, they log in with the invited email address. If they don't have a Lovable account yet, they can create one with that address. Their access is tied to their account after that and is marked with an **EXT** label in the audience list.

These rules apply to external viewers:

* Invites don't expire. See [Remove someone from your audience](#remove-someone-from-your-audience) to take access away.
* Adding an address that is already in the audience sends no second email. To send a fresh invite, remove the person and add them back.
* Workspace members can't be invited as external viewers. Add them by name instead. On Business and Enterprise plans, you can also add the whole workspace or a group.
* On Free and Pro plans, you can invite up to 10 people per project.
* Each address can receive at most 10 invite emails per day from one workspace.
* On Business and Enterprise plans, workspace admins and owners control external viewer invites for the whole workspace from [Workspace settings → Security → Privacy & security → Publishing](https://lovable.dev/settings/privacy-security#publishing). They can set [External viewer invites](https://docs.lovable.dev/features/privacy-and-security-settings.md#external-viewer-invites) to **Off**, or limit invites to specific email domains. Your company's [verified domains](https://docs.lovable.dev/features/verified-domains.md) are always allowed.
* People who were already invited keep their access when an admin or owner changes that setting.
* On Business and Enterprise plans, [Security insights](https://docs.lovable.dev/features/security-insights.md) flags internally published projects that have external viewers, so admins can review who has access.

## Remove someone from your audience

You remove people in the same picker you use to add them. The change reaches your live site when you confirm it in the dialog, the same as an invite does.

**1. Open the audience picker**

In the publish dialog, select the visibility row to open **Who can view your site?**. Select the **Invite only** card (Free and Pro plans) or the **Custom** card (Business and Enterprise plans), then select **View and edit**.

**2. Remove the person**

Hover over their row and select the **X** at the end of it. The row leaves the list, and nothing is saved yet. To put someone back, search for them again and add them.

**3. Apply the change**

Select **Done** to close the picker, then confirm your change in the dialog. The person is no longer in your audience.

You remove a group, an email domain, your whole workspace, or your organization in the same way. Switching the audience to **Public**, to your workspace, or to your organization removes every person, group, and email domain you added. That change also reaches your site only when you confirm it.

Some rows have no **X**. They belong to people whose access comes from the project itself: its owner and the people it is shared with. On a project your whole workspace can open, the workspace row has no **X** either.

These people can open the published app for as long as they can open the project. To take that away, change their project access in the [Share menu](https://docs.lovable.dev/features/share-project.md).

Removing someone does not remove them from your workspace, and it does not delete any request they sent. They can [ask for access again](#approve-requests-to-use-your-published-app).

> [!NOTE]
>
> Someone who already has your app open can keep using it for up to an hour. Lovable checks access again after that and refuses the person who no longer has it.

## Approve requests to use your published app

When someone who is not in the audience opens your published app, they can ask you for access instead of contacting you outside Lovable. They log in to Lovable, see **You don't have access**, and select **Request access**. They add an optional message, then send the request.

> [!NOTE]
>
> This page is about access to an **app you published**, where someone only uses the app. Looking for requests to work on the project with you? See [Project access requests](https://docs.lovable.dev/features/people.md#project-access-requests). The two are different features.

If the app's audience includes your workspace or your organization, a visitor who was invited to your workspace but hasn't accepted yet does not need to request access. Lovable asks them to accept the invitation, then opens the app. See [Find a pending invitation](https://docs.lovable.dev/features/workspace#find-a-pending-invitation).

Requests arrive in your [Inbox](https://docs.lovable.dev/introduction/dashboard-overview.md#inbox-tab), which you open from the user menu under your avatar. Each request shows who asked, their email address, the app they want, and any message they wrote.

Requests go to everyone who can manage that app's audience:

* The project's owner.
* Project editors and above.
* Workspace owners, including on [Restricted](https://docs.lovable.dev/features/project-visibility.md#project-access-options) projects.
* Workspace admins, except on a Restricted project they were not invited to.

Lovable emails the project's owner. When that person has left the workspace or no longer has edit access, Lovable emails the workspace's admins and owners instead. Everyone else sees the request in the Inbox without an email. Lovable emails the requester after you approve or decline.

Select **Approve** to give the person access, or **Decline**. Approving adds them to the app's audience and takes effect immediately, so you do not publish again. Someone still waiting on the page gets into the app within about 10 seconds, without reloading it.

An approved person gets no access to the project itself, and does not join your workspace. If the app is published to your whole workspace, the first approval moves it to a **Custom** audience. That audience includes your whole workspace, so everyone who could open the app still can.

> [!NOTE]
>
> If you unpublish the app while a request is waiting, Lovable refuses the approval. Lovable cannot give access to an app that is not live. The request stays open, so publish the app again, then approve it.

A [workspace policy](https://docs.lovable.dev/features/workspace-policies.md) that does not allow publishing at all blocks approvals too, because approving gives someone access to a published app. A policy that only restricts public publishing leaves approvals working. You can still decline a request either way.

A person whose request you decline can send a new one 24 hours later. Until then, they cannot ask again, and Lovable tells them when they can. A person whose access you [removed](#remove-someone-from-your-audience) can ask again immediately.

## Who can ask for access to your app

Someone who is in neither your workspace nor your [organization](https://docs.lovable.dev/features/organizations) must verify their email address before Lovable accepts the request. Workspace members and colleagues in other workspaces of your organization skip that step.

On Business and Enterprise plans, [External viewer invites](https://docs.lovable.dev/features/privacy-and-security-settings.md#external-viewer-invites) also decides who outside the workspace can ask. With **Off**, nobody outside your workspace can send a request. With **Specific email domains only**, only addresses on the domains you allow can send one. Lovable refuses an approval that the setting no longer allows.

## FAQ

> [accordion] Does publishing expose my project and code?
>
> No. Publishing only makes the app available at the published URL. It does not grant anyone access to your project in the editor or your project code, and it does not make your project automatically remixable.
>
> Access to the editor, source code, project chat history, and unpublished changes is always controlled by [project access](https://docs.lovable.dev/features/project-visibility.md).

> [accordion] How do project access and website access work together?
>
> Project access and website access are **independent settings**. You can combine them in different ways depending on your needs.
>
> * **Project access** controls who can access the **project in the editor**, including source code, project chat history, work in progress, and changes that have not yet been published.
> * **Website access** controls who can visit the **published app** at its live URL.
>
> These are the common combinations:
>
> 1. **Internal team app**
>    * Project access: `Workspace`
>    * Website access: `Workspace`
>    * **Result:** Only workspace members can view and edit the project in the editor and visit the published app.
> 2. **Private work-in-progress, public app**
>    * Project access: `Restricted`
>    * Website access: `Public`
>    * **Result:** Only you and your workspace's owners can view and edit the project in the editor, but anyone with the published URL can visit the published app.
> 3. **Team-built, publicly shared app**
>    * Project access: `Workspace`
>    * Website access: `Public`
>    * **Result:** Only workspace members can view and edit the project in the editor, but anyone with the published URL can visit the published app.
> 4. **Private prototype shared internally**
>    * Project access: `Restricted`
>
>    * Website access: `Workspace`
>
>    * **Result:** Only you and your workspace's owners can view and edit the project in the editor, and only workspace members can visit the published app.
>
> > [!NOTE]
> >
> > Publishing does not change who can access your project in the editor, and project access does not affect who can visit the published app.

> [accordion] Can I restrict who can access my published app?
>
> Yes. On every plan you can restrict your published app to invited people. On Business and Enterprise plans you can also publish it to your whole workspace or to groups. Enterprise workspaces in an organization can also publish it to everyone in the organization. See [Publish to your organization](#publish-to-your-organization).
>
> In the publish dialog, select the visibility row to open **Who can view your site?**. On Free and Pro plans, choose **Invite only** and add people by name or email, up to 10 people per project. On Business and Enterprise plans, choose your workspace to publish internally. You can also choose **Custom** to compose the audience: the whole workspace, specific people, [groups](https://docs.lovable.dev/features/groups.md), and people outside your workspace invited by email. An Enterprise workspace in an organization can add people in the organization as well. Any Enterprise workspace can also add an [email domain](#publish-to-an-email-domain). See [Invite people outside your workspace](#invite-people-outside-your-workspace).

> [accordion] Can I put a password on my published app?
>
> No. A published app has no password. A public app is open to anyone with the link. When you limit who can visit, access works by login. The people you add log in to Lovable with the address you gave access to, and Lovable refuses everyone else. See [Who can see your published app](#who-can-see-your-published-app).
>
> A password is available on [preview links](https://docs.lovable.dev/features/share-project.md#share-preview-links), on Business and Enterprise plans, through **Require a password**. A preview link shows your working version to someone who has no Lovable account. A preview link is different from your published app, and its password does not apply to the live site.
>
> To have people sign in to your app with their own accounts, add [authentication](https://docs.lovable.dev/features/authentication) to the app itself by asking Lovable in the project chat. That is your app's own login, separate from website access.

> [accordion] How do people outside my workspace get access to my internally published app?
>
> Invite them by email from the **Invite only** audience (Free and Pro plans) or the **Custom** audience (Business and Enterprise plans) in the publish dialog. When you select **Publish** (or **Publish changes** on a published project), they receive an email with a link to your site, and people who already use Lovable also get an in-app notification.
>
> To open the site, they log in with the invited email address, or create a Lovable account with that address if they don't have one. Their access doesn't expire, and it is marked with an **EXT** label in the audience list. Adding an address that is already in the audience sends no second email, and workspace members can't be invited as external viewers.
>
> On the Enterprise plan, you can also [publish to an email domain](#publish-to-an-email-domain). Everyone with a verified email at that domain can then open the app after logging in, and Lovable sends no invite email.
>
> Someone who opens the app without access can also ask you to add them, instead of waiting for an invitation. See [Approve requests to use your published app](#approve-requests-to-use-your-published-app).

> [accordion] What happens to website access if I downgrade or cancel my plan?
>
> Downgrading does not take your app offline, and it does not widen who can visit it. The next time you publish changes from the publish dialog, a workspace or group audience switches to **Invite only**, and the dialog warns you first.
>
> See [What happens to my published app if I downgrade or cancel my plan?](https://docs.lovable.dev/features/publish.md#what-happens-to-my-published-app-if-i-downgrade-or-cancel-my-plan) for what happens to domains, credits, and the rest.
