Skip to main content
Project visibility controls who can see, edit, and remix the unpublished version of your project. This includes your code and any work-in-progress changes that haven’t been published yet. Depending on your plan, you can keep a project restricted to yourself, collaborate privately with your workspace, or make it public.
Two kinds of visibilityLovable uses two independent visibility settings that apply to different versions of your app:
  • Project visibility controls access to the unpublished project (editor, code, and work-in-progress).
  • Website access controls who can visit the published app at its live URL.
These settings are independent. Publishing a project does not change its project visibility, and changing project visibility does not affect who can visit the published app.

​
Privacy by default

As of December 2025, all projects default to workspace visibility for all plans. This means your projects are private to your workspace by default and only become public when you choose to change their visibility.

​
Manage project visibility

Project visibility can be managed at both the workspace level and project level.
  • Workspace admins and owners can set the default visibility for all new projects in Settings → Privacy & security → Default project visibility.
  • You can override the workspace default for individual projects at any time in Project settings → Project visibility.

​
Project visibility options

You can set project visibility to:
  • Public (not available for Enterprise)
    Anyone can view and remix the unpublished project.
  • Workspace (default for all plans)
    Only workspace members can view and collaborate on the unpublished project. Ideal for team collaboration while keeping work private and secure.
  • Restricted (available for Business and above)
    Only you can see and edit the unpublished project. Use this for early exploration, prototyping, or personal experiments. You can change it to workspace visibility when you’re ready to share and collaborate with your team.
Important note:
  • Before November 6, 2025: Projects were public by default for free plans, and only paid workspaces could change visibility.
  • After November 6, 2025: New projects default to workspace visibility for all plans, and all workspaces can update visibility of existing projects.
  • From December, 2025: All projects default to workspace visibility for all plans.

​
FAQ

No, publishing only makes the app available at the published URL. It does not grant anyone access to your project or code, and publishing your project does not make it automatically remixable. Access to the editor, code, and unpublished changes is always controlled by project visibility. Only projects with public project visibility can be viewed or remixed by anyone.Website access to the published app is controlled separately. For more information, see Publish your app.
No. Website access settings control who can visit the published URL. See Publish your app for more information.
Yes, you can change your project’s visibility at any time. Go to Project settings → Project visibility and select a different option, depending on your plan. The change takes effect immediately, and you can switch between visibility settings as often as needed.
Workspace visibility allows all workspace members to view and collaborate on the unpublished project. This is ideal for team projects where you want input and contributions from colleagues.Restricted visibility means only you can see and edit the unpublished project. Other workspace members won’t see it in the workspace project list. This is useful for early-stage ideas, personal experiments, or prototypes you’re not ready to share yet. You can change it to workspace visibility when you’re ready to collaborate.
Yes. Create the project with Restricted visibility. The project will only be visible to you.When you’re ready to share, click Share and invite specific people, assigning roles as needed.