Skip to main content
Project settings is where you manage a single project: its name and URL, project type, monitoring, publishing options, sharing toggles, Git connection, domains, knowledge, and skills. This page walks through the settings tab by tab so you know exactly where each option lives.

Where to find project settings

You can open a project’s settings from several places. You need edit access to the project for all of them. In the editor:
  • Sidebar: Click the menu icon in the top-left corner to open the sidebar, then select Settings.
  • Chat actions menu: Click the + button next to the chat input and choose Project → Settings. See Chat actions.
  • More menu: Select More in the project toolbar, then Settings. General opens inside the editor. The same group also lists Knowledge, Domains, and Git. See The More menu.
  • Draft switcher: Click your project’s name at the top of the editor, then the Project settings button on the top row of the switcher. See Project name and drafts.
  • Keyboard: Press Cmd+. (Mac) or Ctrl+. (Windows/Linux).
Outside the editor:
  • Dashboard: Open a project card’s three-dot menu and select Settings. See Manage projects from the dashboard.
  • Sidebar project list: On the dashboard or in the editor, hover a project in the sidebar, click its button, and select Settings.
  • Lovable mobile app: Tap the project’s name in the editor and choose Settings. See Lovable mobile app.
From anywhere in Lovable, press Cmd+K (Mac) or Ctrl+K (Windows/Linux) to open the command palette and type the name of the setting you’re looking for.
Access control does not live here. Who can access the project, collaborators, invite links, and share preview links all live in the Share menu in the top right of the editor. See Share your project.
To view or edit the source code Lovable generates for your app, open the Code tab in the project toolbar, not Project settings. See Code editor.

General tab

The General tab opens by default and contains most settings, grouped into sections.

Details

  • Project name: Rename your project. Lovable names new projects automatically, and the name is visible only inside your workspace, never to visitors of your published app. Renaming only changes the display name, not your project’s URL.
  • URL subdomain: Change the subdomain of your published lovable.app address, which is where visitors find your app once you publish.
  • Owner: Shows who owns the project, with a link to their profile. See project roles.
  • Messages count and AI edits count: Read-only counters showing how much you’ve built in this project.
  • Use as a template: Turn your project into a template that others in your workspace can start from. Available on Business and Enterprise plans. See Design templates. On workspaces that use design systems, this appears as a Project type selection instead, with Design system as a third option.
  • Design system (paid plans): The design system Lovable builds this project with, so new UI matches your organization’s components and styles. Click Attach design system to pick one, or Manage design system once attached. See Design systems.

Project monitoring

  • Project monitoring: Have Lovable review your project’s code and recent visitor errors on a daily or weekly schedule, and alert you to important issues in the editor and by email. Disabled by default, available on Pro plans and above. See Project monitoring.

Preview

  • Live preview: Run your app live in the editor preview so changes appear as Lovable works. Enabled by default. When you disable it, the preview shows the most recent completed version of your app instead, and switching between versions in version history doesn’t restart the live environment. You can re-enable it at any time. See Turn off the live preview.

Publishing

  • Project category: Categorize what kind of app this is, which helps Lovable and directories present it correctly.
  • Hide Lovable badge: Removes the “Edit with Lovable” badge from your published app. Available on Pro plans and above. If your workspace later moves to a plan that doesn’t include this, the badge comes back the next time you publish the project. Sites that are already live stay unchanged until you republish them.
  • Visitor analytics: Collect visitor data for your published app, which powers the Analytics view in the editor. Enabled by default. When you disable it, Lovable stops collecting and the Analytics view shows no new data.
  • AI app context: Let Lovable use context from your app’s AI calls to debug and improve its AI features. Secrets are removed from the logs automatically, and logs are kept for 90 days. See AI features.
  • Auto-fix security issues: Let Lovable automatically fix low-risk issues found by security scans, so simple findings don’t wait on you. Workspace owners and admins can set a workspace-wide default in Workspace settings → Privacy & security, and when they lock it there, the project setting can’t be changed here.
  • Unpublish project: Takes your published app offline. The button is available only while the project is published. See Publish your project.

Sharing

  • Project access: A shortcut only: the Open share menu button takes you to the Share menu, where you control who can view and edit the project. See Share your project.
  • Public remixing: Control whether anyone with your project’s link can create their own copy of it. Disabled by default. See Remix a project.
  • Cross-project sharing: Controls whether your other projects can reference this one as context. Workspace admins can disable this workspace-wide. See Cross-project referencing.

Project actions

Transfer project ownership

Click Transfer ownership and pick the new owner. The new owner must be an active member of the workspace with an owner, admin, or editor role: viewers, external collaborators, and people with pending invites aren’t eligible. After the transfer, the new owner has full control of the project, and what you can still do depends on your workspace role. If the project’s access is set to Restricted, only the owner, invited collaborators, and workspace owners can open it, so after the transfer you lose access to it entirely unless you’re a workspace owner. See Project access. If an owner leaves the workspace, their projects transfer automatically to the member with the highest role, and if an admin or owner removes them, that person chooses who inherits them. See project roles. You can also hand over several projects at once from the dashboard, which is quicker when someone is leaving or you’re consolidating projects. See Change the owner of several projects.

Move a project to another workspace

Click Move on the Move workspace row and pick the destination workspace. You can also start a move from the dashboard: open a project card’s menu and select Transfer to workspace, or select several projects to move them together. You can move projects you own, and workspace owners (plus workspace admins on paid plans) can move any project they can access. On Enterprise workspaces, project owners additionally need the Editor project transfers setting turned on. The move dialog includes a Transfer project collaborators checkbox:
  • Off (default): people invited directly to the project, and any pending project invites, are removed when the project moves. Access through workspace membership is not affected.
  • On: Lovable keeps direct collaborators and pending invites when the destination workspace allows their role and you have permission to grant it there. Some collaborators may still be removed, for example when the destination workspace’s External project collaborators policy doesn’t allow their role.
Two more things change during a move: the project leaves its dashboard folder, and its access setting resets to the destination workspace’s default, so check Project access after the move if the project should stay restricted.

Danger zone

  • Delete project: Permanently deletes the project. To confirm, you type the project’s name.
Deleting a project is permanent. You cannot restore a deleted project, so download your code or remix the project first if you might need it later.

Git tab

The Git tab is where you connect your project to a GitHub, GitLab, or Bitbucket repository and manage the connection. The sync is two-way: Lovable pushes every change it makes to the repository, and commits you push to the synced branch flow back into Lovable. That gives you a full copy of your code outside Lovable and lets developers on your team work with their own tools. See Git sync for how the sync works.

Domains tab

The Domains tab is where you manage the web addresses of your published app. You can connect a domain you already own, buy a new domain directly through Lovable, and choose a primary domain that all your project’s other addresses redirect to. You can also buy and connect a domain by asking Lovable in the project chat. You can set a primary domain only in this tab. Custom domains are available on paid plans. See Set up a custom domain, or follow Launch your site on a custom domain for the full path from publishing to a live site on your domain.

Knowledge tab

The Knowledge tab is where you write your project’s instructions and guidelines. Lovable follows them in every request, so use this tab to describe your product, audience, and preferences once instead of repeating them in chat. Anyone with edit access can update project knowledge, and the same tab shows your workspace-wide knowledge. The Knowledge section under More shows this project’s knowledge only. See Knowledge. Open the Knowledge tab from any of these places:
  • Settings → Knowledge, under Customization in the settings sidebar
  • Project → Knowledge in the Chat actions menu in the editor
  • More → Settings → Knowledge in the project toolbar

Skills tab

Open Settings → Skills, also under Customization in the settings sidebar, to manage the reusable instruction sets available in this project, such as a launch checklist or a release notes format. Workspace owners and admins manage which skills exist. See Skills.

FAQ

In the Share menu in the top right of the editor. That’s where you manage project access, collaborators, invite links, and share preview links. The Project access row in settings is a shortcut that opens the same menu. See Share your project.
Open Project settings → General and edit Project name. In the editor, you can also press Cmd+Shift+. (Mac) or Ctrl+Shift+. (Windows/Linux). Another route is the sidebar: hover the project and choose Rename from its menu. Renaming changes the display name only. To change your published address, edit URL subdomain instead.
  • Move workspace sends the project to another workspace you belong to.
  • Transfer ownership keeps the project in the same workspace but makes another workspace member the owner.
  • Remix project creates a separate copy of the project to build on, in this workspace or another one. See Remix a project.
No. Deleting a project is permanent, which is why Delete project asks you to type the project’s name to confirm. If you might need the project later, download the code or remix it before deleting.