Skip to main content
Team settings help team admins control how shared workspaces operate across Bolt. These settings shape what teammates can access, how projects are published, which integrations are allowed, and what rules Bolt follows when working with your code. Team settings create a consistent environment that supports collaboration and keeps projects aligned with internal practices.

​
Set project visibility

By default, all new Bolt projects are private. As a team admin, you can limit your team’s ability to change visibility levels.
When you set a project to public, the Bolt project URL becomes publicly accessible and may appear in search engine results. See General project settings to learn more.
Sharing links to Teams projects works differently than sharing project links between unrelated accounts:
  • Private: Teammates can open and edit the project. Any changes they make overwrite the shared project. Non-teammates can’t open the link.
  • Secret: Teammates can open and edit the project, and their changes overwrite the shared version. Non-teammates can open the project too, but their edits automatically create a new fork instead of changing the original.
  • Public: Teammates can open and edit the project, and their changes overwrite the shared version. Non-teammates can open the project, and their edits create a new fork automatically.
To avoid overwriting each other’s changes, coordinate before editing or use forks for independent updates.
To change permitted visibility levels for your team members, follow these steps:
  1. Log in to your Teams account and open the Bolt homepage.
  2. Hover over the left side of your screen, then click Settings.
  3. Click Team under your team’s name.
  4. Click the gear icon in the top right to open team settings.
  5. Under Team settings, click on (or drag-and-drop the slider) your preferred Project visibility option. The project visibility slider in Team settings

​
Set the default publishing provider

By default, team members can choose which publishing provider to use for their projects. Team admins can set a default provider — Bolt or Netlify — for all team projects.
To change the default provider:
  1. Log in to your Teams account and open the Bolt homepage.
  2. Hover over the left side of your screen, then click Settings.
  3. Click Team under your team’s name.
  4. Click the gear icon in the top-right corner of the window.
  5. From the Team-wide deploy provider dropdown, select User Specified, Bolt Cloud, or Netlify.
When a default publishing provider is set, team members can’t choose between providers in their project’s Domains & Hosting settings. Instead, they see their default provider listed along with a note advising them to contact their admin to request a change.

​
Set published site visibility

By default, team members choose whether to publish their site as public or private. Team admins can override this and enforce a single visibility option for all team projects.
The Integration Controls section in Team settings in Bolt.
  1. Log in to your Teams account and open the Bolt homepage.
  2. Hover over the left side of your screen, then click Settings.
  3. Click Team under your team’s name.
  4. Click the gear icon in the top-right corner of the window.
  5. Under Published site visibility dropdown, select an option:
    • User specified — Members choose visibility when publishing.
    • Private only — All published sites are private.
    • Public only — All published sites are public.
When set to Private only or Public only, team members can’t edit the site visibility in the Publish menu.

​
Share databases between team members

Sharing Bolt databases between team members isn’t currently supported.
If your project requires shared database access or collaborative editing, use Supabase from the start. You can also claim your Bolt database in Supabase if you’ve already started a Bolt database you’d like to keep using.

​
Enable or disable integrations

By default, team members can decide which integrations to use in their Bolt projects. If needed, team admins can limit or turn off access to specific third-party integrations for the entire team. To manage which integrations your team can use:
  1. Log in to your Teams account and open the Bolt homepage.
  2. Hover over the left side of your screen, then click Settings.
  3. Click Team under your team’s name.
  4. Click the gear icon in the top-right corner of the window.
  5. Scroll down to the Integration Controls section, then use the toggles to turn on or turn off specific integrations.
The Integration Controls section in Team settings in Bolt.

​
Set a team prompt

A team prompt defines team-wide rules. You can use it to create a code of conduct and best practices.
Only team admins can view or modify the team prompt.
To set the team prompt:
  1. Log in to your Teams account and open the Bolt homepage.
  2. Hover over the left side of your screen, then click Settings.
  3. Click Knowledge under your team’s name.
  4. Click Team prompt. The team prompt editor in Knowledge settings
  5. Create a new team prompt or modify the existing one.
  6. Click Save prompt.
Your changes are discarded if you close the modal before clicking Save prompt.

​
Add package prompts

Package prompts give Bolt additional context about the packages your team uses. They inform Bolt about internal libraries and help fill in knowledge gaps about third-party packages where Bolt may have limited information about the package or a specific version.
Only team admins can view or modify package prompts.
To create package prompts:
  1. Log in and open the Bolt homepage.
  2. Hover over the left side of your screen, then click Settings.
  3. Click Packages knowledge under your team’s name.
  4. Click + Add package instructions. The Add package instructions button in Packages knowledge settings
  5. Enter the exact package name as it appears in package.json. The new package prompt form with package name and instructions fields
  6. Enter your prompt and save.

​
Connect private NPM registries

You can integrate Bolt with any private NPM registry that’s accessible from the internet without proxies or VPNs. To connect a registry to your Teams account:
  1. Get the registry URL and access token from your provider. Check your provider’s documentation for specific steps.
  2. Log in and open the Bolt homepage.
  3. Hover over the left side of your screen, then click Settings.
  4. Click Private registries. The private registries page in Teams settings
  5. Click Add private registry.
  6. Fill in the URL, token, and optional scopes. The private registry configuration form with URL, token, and scope fields
  7. Save the new registry.
If you leave the scope field empty, all package installations for your team run through your private registry. If you fill in the scope field, only package installations for the selected scope run through your private registry.
Bolt keeps registry credentials secure in your account settings and doesn’t create or update an .npmrc file. Team members need to manage their .npmrc files for local development.

​
Copy personal projects to Teams

To duplicate a personal project into a Teams plan, follow these steps.
Duplicating creates a copy of the project files. It doesn’t retain chat history or context.
  1. Log in to your Teams account on Bolt.
  2. Go to StackBlitz and open your Bolt collection page: https://stackblitz.com/@USERNAME/collections/bolt.
  3. Click the project you want to edit.
  4. Click Open in bolt.new | AI. When you send a new prompt, Bolt automatically forks the project to your team.
You can also manually fork it to your team on StackBlitz by opening the Fork dropdown menu, selecting your team, then clicking Open in bolt.new | AI.