Control who can publish externally

How it works

How Control who can publish externally works, drawn only from its official release notes.

1. 01

   What it does

   On Enterprise plans, admins can now restrict external publishing to: This improves security and supports governance for organizations handling sensitive data.

2. 02

   What the release notes list

   Admins & owners; Owners only.

3. 03

   Who gets it

   The source does not say which plans include it. Check your workspace before relying on it.

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 Control who can publish externally working in a real project rather than a sandbox.

   Set up Control who can publish externally in this project — on Enterprise plans, admins can now restrict external publishing to: This improves security and supports governance for organizations. 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

   Review it before you publish

   Control who can publish externally 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 Control who can publish externally before I publish. Check admins & owners and owners only, 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. 03

   Decide whether it fits your project

   Worth five minutes before you wire anything in. Control who can publish externally sits in Security, and not every project needs it.

   I am building the project in this workspace. Given that Control who can publish externally on Enterprise plans, admins can now restrict external publishing to: This improves security and supports governance for organizations, 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.

Frequently asked

• What is Control who can publish externally?

  Control who can publish externally is Lovable's Security feature: On Enterprise plans, admins can now restrict external publishing to: This improves security and supports governance for organizations handl…. On Enterprise plans, admins can now restrict external publishing to: This improves security and supports governance for organizations handling sensitive data.

• Is Control who can publish externally GA or in beta?

  Control who can publish externally is generally available (GA) on Lovable.

• What Lovable plan includes Control who can publish externally?

  The atlas has not verified which Lovable plans include Control who can publish externally. Check Lovable's pricing page.

• When did Control who can publish externally launch?

  Control who can publish externally launched on Dec 10, 2025.