Granular Publishing Access

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

   Stand it up from scratch

   You have read the record and want Granular Publishing Access working in a real project rather than a sandbox.

   Set up Granular Publishing Access in this project — restrict published-app access to specific people or groups. 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. 02

   Internal-only apps for one team

   The record lists this as one of the jobs Granular Publishing Access is meant for, so it is a fair first test of whether it fits your app.

   In this project, use Granular Publishing Access for internal-only apps for one team. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   Granular Publishing Access 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 Granular Publishing Access before I publish. Check member- and group-level access and per-app restriction lists, 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.

4. 04

   Tight launch control

   A second job the record lists for Granular Publishing Access, useful once the first path works.

   Extend this project so Granular Publishing Access also covers tight launch control. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

   Expected outcome

   A second path built on the same setup, plus a note on what was shared and what was added.

Frequently asked

• What is Granular Publishing Access?

  Granular Publishing Access is Lovable's Publishing feature: Restrict published-app access to specific people or groups. Granular Publishing restricts published-app access to specific workspace members or groups rather than the entire workspace or public.

• Is Granular Publishing Access GA or in beta?

  Granular Publishing Access is generally available (GA) on Lovable.

• What Lovable plan includes Granular Publishing Access?

  Granular Publishing Access is available on Lovable's Business and Enterprise plans plan.

• When did Granular Publishing Access launch?

  Granular Publishing Access launched on Apr 24, 2026.

• Project Visibility & Public RemixingSame category, also GA · Apr 2026
• CDN / Reverse Proxy DomainsSame category, also GA · Apr 2026
• Branded app URLsSame category, also GA · May 2026