Skip to content

The Lovable Feature AtlasIndependent community catalog

Atlas
Security

Viewer-only access to published apps

GASecurityReleased Sep 2026All plansSource: docs.lovable.dev

Viewer-only access to published apps is Lovable's Security feature: Allow external users to view apps without editing rights.

This feature enables workspace admins to set apps to be viewable only to external users. It helps in showcasing the app without risks of unauthorized modifications and allows easier sharing of project details.

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

  1. Stand it up from scratch

    You have read the record and want Viewer-only access to published apps working in a real project rather than a sandbox.

    Set up Viewer-only access to published apps in this project — allow external users to view apps without editing rights. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

    Expected outcome

    A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

  2. Review it before you publish

    Viewer-only access to published apps is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

    Review how this project uses Viewer-only access to published apps before I publish. Check limit external user access to view-only and retain full control over editing by workspace members, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

    Expected outcome

    A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

  3. Decide whether it fits your project

    Worth five minutes before you wire anything in. Viewer-only access to published apps sits in Security, and not every project needs it.

    I am building the project in this workspace. Given that Viewer-only access to published apps allow external users to view apps without editing rights, tell me honestly whether it fits what I am building, including the cases where I should not use it. If it does fit, give me the single smallest first step.

    Expected outcome

    A direct yes or no with the reasoning, the cases against it, and one first step. Treat a hedged answer as a no.

Capabilities

  • Limit external user access to view-only
  • Retain full control over editing by workspace members
  • Easily share apps for demos or reviews
  • Maintain project integrity and security
  • Review visibility settings regularly
  • Control access during project sharing

The link to lovable.dev uses a referral code. The atlas is otherwise unsponsored.

Frequently asked

  • What is Viewer-only access to published apps?

    Viewer-only access to published apps is Lovable's Security feature: Allow external users to view apps without editing rights. This feature enables workspace admins to set apps to be viewable only to external users.

  • Is Viewer-only access to published apps GA or in beta?

    Viewer-only access to published apps is generally available (GA) on Lovable.

  • What Lovable plan includes Viewer-only access to published apps?

    Viewer-only access to published apps is available on all Lovable plans.

  • When did Viewer-only access to published apps launch?

    Viewer-only access to published apps launched on Sep 1, 2026.

Related in Security

See all →
Post on XLinkedIn

What Lovable Shipped

One email a week. Every new feature. Nothing else.

A curated Monday roundup of every Lovable feature added or promoted to GA in the past week — pulled straight from the atlas.

No spam. Unsubscribe anytime. Independent, not affiliated with Lovable AB.