> ## 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 project access > Control who can view, remix, or collaborate on your projects. Choose whether projects are accessible to all workspace members, or restricted to invited users only. Project access (previously project visibility) controls who can view, edit, and remix **your project in the editor**. This includes access to your source code, chat history, work in progress, and changes that have not yet been published. Depending on your plan, you can keep a project restricted to invited users only or collaborate privately with your workspace. **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, 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. ## Workspace visibility by default As of December 2025, all workspaces have their **default project access** set to **workspace**. This means your projects are private to your workspace and can only be accessed by workspace members by default. ### Restrict project access On **Business and Enterprise plans**, you can choose to restrict projects to invited users only, both on **workspace level** and **project level**. * Workspace **admins and owners** can set the **default project access** for all new projects in **Settings → Privacy & security → Default project access**. * You can override the workspace default for individual projects at any time: * From the prompt input box on the dashboard **when creating new projects** * From the **Share** button in the top bar of any **existing project**. See [Share a project](/features/share-project) for more information. Keep in mind that workspace owners have full access to **all** projects in the workspace and can view and edit them. ### Project access options | Default project access | Project-level access | Description | | ----------------------------------------------------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Workspace**
(default for all plans) | Workspace can edit | All **workspace members and explicitly invited collaborators can view, remix, or edit the project based on their role.**
Ideal for team collaboration while keeping work private and secure. | | **Restricted**
(available for Business and Enterprise) | Workspace has no access | **Only the owner and explicitly invited collaborators can view, remix, or edit** the project based on their role.
Use this for early exploration, prototyping, or personal experiments. You can give access to the workspace when you’re ready to share and collaborate with your team.
| ## Share a project with internal or external collaborators The **Share dialog** is where you open up a project to others: workspace members, external collaborators, or anyone with a link. It is accessible from the **Share** button in the top bar of any project. See [Share a project](/features/share-project) for more information. ## Enable public remixing When public remixing is enabled, anyone with the project link can copy and remix the project. You can disable this at any time. * People always **copy the latest version** when they remix. They can't edit your project, and the original stays unchanged. * People can **view your project's source code** when they remix it. Make sure it does not include passwords, API keys, or personal data. To let others copy and remix your project, go to **Project settings** and turn on **Enable public remixing**. **Important note:** * **Before November 6, 2025:** Projects were **public by default** for free plans, and only paid workspaces could change visibility. * **Starting November 6, 2025:** New projects default to **workspace visibility** for all plans, and all workspaces can update visibility of existing projects. * **As of December, 2025:** All workspaces have their **default project visibility** set to **workspace**. **Default project visibility** has been updated to **workspace** for all Lovable workspaces that previously had default project visibility set to public. * **Starting April 22, 2026**: You can no longer create public projects. Public project visibility has been completely removed. All public projects have been updated to **workspace** visibility. ## FAQ 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, chat history, and unpublished changes is always controlled by **project access**. Access to the published app is controlled separately through website access settings. For more information, see [Publish your app](/features/publish). No. Project access controls who can access your project in the editor. Access to the live app at its published URL is managed separately through website access settings. See [Publish your app](/features/publish) for more information. 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, 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. Below are common configurations: 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: `Anyone` **Result:** Only you can view and edit the project in the editor, but anyone with the published URL link can visit the published app. Keep in mind that workspace owners have full access to **all** projects in the workspace and can view and edit them. 3. **Team-built, publicly shared app** * Project access: `Workspace` * Website access: `Anyone` **Result:** Only workspace members can view and edit the project in the editor, but anyone with the published URL link can visit the published app. 5. **Private prototype shared internally** * Project access: `Restricted` * Website access: `Workspace` **Result:** Only you can view and edit the project in the editor, and only workspace members can visit the published app. Keep in mind that workspace owners have full access to **all** projects in the workspace and can view and edit them. **Key reminder:** Publishing does not change who can access your project in the editor, and project access does not affect who can visit the published app. Yes, you can change the project access at any time from the **Share** button in the top bar of any project. See [Share a project](/features/share-project) for more information. Yes. Create the project with **Restricted** access. The project will only be visible to you. When you’re ready to share, click **Share** and invite specific people or [groups](/features/groups), assigning roles as needed. See [Share a project](/features/share-project) for more information. Keep in mind that workspace owners have full access to **all** projects in the workspace and can view and edit them.