Privacy & security settings

1. 1

   Go to 'Settings' in your Lovable workspace.

   This is where all workspace-wide configurations are located.

2. 2

   Navigate to 'Security' and then select 'Privacy & security'.

   This tab contains all the controls for member access, publishing, sharing, and data protection.

3. 3

   Review the settings under 'Access & membership' to control how people join and interact with projects.

   This section lets you set default project visibility, restrict who can invite new members, manage invite links, and control external collaborators.

4. 4

   Check the 'Publishing' settings to define who can publish projects and what audience they reach by default.

   This helps you manage public exposure of your projects and enforce security checks before publishing.

5. 5

   Adjust 'Security automation' settings to enable or disable automatic fixes for security issues.

   Automated security can help maintain project integrity without manual intervention.

6. 6

   Configure 'Abandoned projects' settings if you want to automatically identify and delete inactive projects.

   This helps keep your workspace tidy and removes old, unused projects that might pose a security risk or clutter your environment.

7. 7

   Review 'Sharing' settings to control public preview links, code downloads, and cross-project sharing.

   These settings determine how easily project content can be shared or reused, both internally and externally.

8. 8

   Check 'Lovable MCP server' and 'MCP connectors' settings if you use external tools or data sources with Lovable.

   These controls manage how third-party applications and external data can interact with your workspace.

9. 9

   Click 'Save' after making any changes to apply them.

   Changes are not applied until you explicitly save them.

I need to review and adjust my workspace's privacy and security settings. Please guide me through the options for managing member access, project publishing, external sharing, security automation, and abandoned projects. I want to ensure our projects are secure and comply with our organizational policies.

Workspace

Your team's shared area in Lovable where projects are created and managed.

External collaborators

People who are not full members of your Lovable workspace but are invited to work on specific projects.

PII

Personally Identifiable Information, which is any data that could be used to identify a specific person.

SSO

Single Sign-On, a method that allows users to access multiple applications with one set of login credentials.

JIT provisioning

Just-In-Time provisioning, where user accounts are automatically created in Lovable the first time a user signs in through an identity provider.

SCIM provisioning

System for Cross-domain Identity Management, a standard that helps automate the exchange of user identity information between different systems.

MCP

Model Context Protocol, a way for external tools to connect and interact with your Lovable projects and data.

• Changing 'Default project access' does not change existing projects; you must update them individually.
• Restricting workspace invitations only affects manual invites, not automatic provisioning methods like JIT or SCIM.
• Turning off 'Workspace discovery' does not clear pending access requests; you must review and deny them manually.
• If 'Public member profiles' is disabled in any Enterprise workspace a user belongs to, their profile remains hidden globally, even if other workspaces allow public profiles.
• If 'Editor project transfers' is enabled, editors can move projects out of your organization's control.
• If 'Who can publish externally' is set to 'Owners only', only the owner can change this setting, potentially locking out admins.
• Preview links bypass 'Default website access'; even for workspace-only projects, an enabled preview link allows external viewing without authentication.
• Disabling 'Code downloads' only affects zip downloads from Lovable, not access to connected GitHub/GitLab repos or viewing code in the editor.