Workspace admin settings
Workspace admin settings let you control how your team works in Lovable, from who can access what to how projects are built and secured. These settings apply across your entire workspace and define defaults for all members.
Workspace owners and admins need this to manage their Lovable workspace effectively.
Do this, in order
- 1
Go to lovable.dev/settings or click the workspace switcher at the top-left of your dashboard and select "Workspace settings".
This is the central place to access all workspace-wide controls.
- 2
Use the sidebar to navigate between different sections like 'General', 'Billing and usage', 'Access', 'Customization', 'Build & deploy', and 'Security'.
Each section groups related settings for easier management, allowing you to configure specific aspects of your workspace.
- 3
Adjust settings such as your workspace name, avatar, default monthly member credit limits, or enable branded app URLs under 'General'.
These settings define your workspace's identity and basic operational rules.
- 4
Manage your subscription, view credit usage, and handle billing details under 'Billing and usage'.
This ensures your workspace remains active and funded according to your team's needs.
- 5
Control who has access to your workspace, manage members, groups, and set up single sign-on (SSO) under 'Access'.
This secures your workspace and streamlines user management and authentication.
- 6
Define workspace-level knowledge, skills, templates, design systems, and connector rules under 'Customization'.
These settings standardize project creation, ensure consistency, and govern how your workspace integrates with other tools.
- 7
Configure Git connections, build secrets, managed npm registries, and MCP server settings under 'Build & deploy'.
This manages shared development configurations and integrations essential for building and deploying projects.
- 8
Set workspace-wide security policies, monitor risks, and view audit logs under 'Security'.
This protects your projects and data, ensures compliance, and provides transparency into workspace activity.
- 9
Manage how your workspace connects to external tools and services, including custom connectors, under 'Connectors'.
This allows you to control integrations and ensure secure and appropriate use of external services.
Paste this into your project
Hey Lovable, I need to manage my workspace settings. Can you help me with the following: 1. **Change Workspace Name**: Update my workspace's display name to "My Team's Projects". 2. **Set Default Credit Limit**: Set a default monthly build credit limit of "500" for all new members. 3. **Enable Branded App URLs**: Turn on the option to publish apps under a workspace-branded subdomain. 4. **Invite New Member**: Invite "new.member@example.com" to the workspace as an "Editor". 5. **Review Security Center**: Provide a summary of the top 3 security findings across my projects. 6. **Check Audit Logs**: Show me all actions performed by "admin@example.com" in the last 7 days.
Words decoded
- Workspace handle
- A unique public name for your workspace used in web addresses, like a username for your team's Lovable space.
- Build credits
- Units used to pay for the computing power needed to create or update your apps within Lovable.
- Run credits
- Units used to pay for hosting, built-in backend services, and AI features when your apps are live and being used.
- SCIM
- A standard way for different computer systems to talk to each other to automatically manage user accounts and groups, like adding or removing people from your Lovable workspace when they join or leave your company.
- SAML
- A standard way for users to log in to multiple applications with a single set of credentials, often used by companies to let employees access Lovable using their company login.
- OIDC
- Another standard way for users to log in, similar to SAML, often used for web and mobile applications to verify a user's identity.
- Command palette
- A quick search bar that lets you type commands or search for settings and jump directly to them, like a super-powered search for actions within Lovable.
- Environment variables
- Secret pieces of information, like passwords or API keys, that your apps need to work but shouldn't be visible in your code. They are stored securely and only used when your app is being built or run.
- npm registry
- A central online library where developers can share and download reusable code packages. A 'managed registry' means your workspace has its own private version of this library.
- MCP server
- A special connection point that allows AI tools like ChatGPT or Claude to securely interact with your Lovable projects and data.
- Audit logs
- A detailed record of all actions taken within your workspace, showing who did what, when, and to which resource, useful for security and compliance.
Where people get stuck
- Changing your workspace handle may break existing links to your projects or profile pages.
- Deleting a workspace is permanent after a 60-day grace period and removes all projects and member access.
- Leaving a workspace is not possible if you are the only owner or if it's your only workspace.
- Not understanding the difference between build credits (for creating apps) and run credits (for live apps) can lead to unexpected usage charges.
- Incorrectly configuring access controls or SSO can lock users out or grant unintended access.
- Forgetting to set individual credit limits can lead to members exceeding the default workspace limit if not managed.
- Not regularly reviewing security settings and audit logs can expose your workspace to risks.
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.