Folder visibility controls

How it works

How Folder visibility controls works, drawn only from its official release notes.

1. 01

   What it does

   You can now set folder visibility to: You can only configure visibility on the top-level folder.

2. 02

   What the release notes list

   Workspace visibility: All workspace members can see and add projects to the folder; Private visibility: Only you can see and add projects to the folder.

3. 03

   Still in beta

   Behavior can change before general release. Test it on a copy first.

4. 04

   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 Folder visibility controls working in a real project rather than a sandbox.

   Set up Folder visibility controls in this project — you can now set folder visibility to: You can only configure visibility on the top-level folder. It is still in beta, so build the smallest version that proves it works, tell me exactly what you changed, and flag anything I have to switch on myself.

   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

   Folder visibility controls 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 Folder visibility controls before I publish. Check workspace visibility: All workspace members can see and add projects to the folder and private visibility: Only you can see and add projects to the folder, 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. Folder visibility controls sits in Workspace, and not every project needs it.

   I am building the project in this workspace. Given that Folder visibility controls you can now set folder visibility to: You can only configure visibility on the top-level folder, 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 Folder visibility controls?

  Folder visibility controls is Lovable's Workspace feature: You can now set folder visibility to: You can only configure visibility on the top-level folder. You can now set folder visibility to: You can only configure visibility on the top-level folder.

• Is Folder visibility controls GA or in beta?

  Folder visibility controls is currently in beta on Lovable.

• What Lovable plan includes Folder visibility controls?

  The atlas has not verified which Lovable plans include Folder visibility controls. Check Lovable's pricing page.

• When did Folder visibility controls launch?

  Folder visibility controls launched on Feb 23, 2026.