Privacy & security settings
Workspace owners and admins can manage organization-wide rules for who can see projects, download code, and publish apps. These controls keep sensitive work private and prevent apps from going live with unresolved security flaws.
Workspace admins and owners who need to govern member access, protect code, and set publishing guardrails across all projects.
Do this, in order
- 1
Open Workspace settings, select Security, and click Privacy & security.
This is where all organization-level access, sharing, integration, and publishing controls are managed.
- 2
Review the Access tab to configure default project visibility, invite link permissions, and two-factor authentication.
Stricter defaults prevent new projects and invitations from inadvertently exposing internal work to outsiders.
- 3
Check the Sharing tab to enable or disable public preview links, code zip downloads, and cross-project references.
Restricting code downloads and preview links keeps proprietary code and in-progress work inside your team.
- 4
Navigate to the Publishing tab and turn on 'Block publishing with critical issues'.
This prevents projects from being deployed to the web while known critical security vulnerabilities remain unfixed.
- 5
Click Configure under App login methods to choose which sign-in options projects in your workspace are allowed to use.
Locking down disallowed login providers ensures all apps built by your team meet company security standards.
Paste this into your project
Audit this application for any security vulnerabilities, exposed secrets, or unprotected routes. Fix any identified security issues and ensure proper access controls are applied so the project is ready for publishing.
Words decoded
- Two-factor authentication (2FA)
- A login security step that requires a temporary passcode from your phone or app in addition to your password.
- SSO
- Single Sign-On, a feature that lets employees log in using their company credentials like Google Workspace or Okta.
- JIT / SCIM provisioning
- Automated tools that create and update team member accounts automatically through your corporate identity provider.
Where people get stuck
- Changing the default project access setting only applies to future projects and does not change the visibility of projects that already exist.
- Preview links ignore workspace-only access rules, meaning anyone with an active preview link can see the app unless preview links are disabled or password-protected.
- Ignoring a security scan finding lets you bypass the publish block, but it does not actually fix the underlying security vulnerability.
The short version, steps, decoder and prompt on this page are written automatically from Lovable's own documentation and can lag or misread it. The official page is always the authority.