Skip to main content
Project controls help team admins guide 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 should follow when working with your code. This gives teams 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.
Teams-specific editing 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 will overwrite the shared project. Non-teammates cannot 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, it’s best to coordinate before editing or use forks for independent updates.
How to change team visibility settings 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. Set Max Visibility Gi

​
Sharing databases between team members

Sharing Bolt databases between team members isn’t currently supported.
If your project requires shared database access or collaborative editing, it’s best to 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.

​
Set the default publishing provider

By default, team members can choose which publishing provider to use for their projects. However, team admins can also choose to set a default provider, Bolt or Netlify, for all team projects.
Follow the steps below 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. Scroll down to the Team-wide deploy provider section, then select User Specified, Bolt Cloud or Netlify from the drop-down menu.
When a default publishing provider is set, team members cannot choose between providers in their project’s Domains & Hosting settings. Instead, they will see their default provider listed along with a note advising them to contact their admin if they need to request a change.

​
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. Use the steps below 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 enable or disable specific integrations.
Screenshot of managing Team integrations in Team settings in Bolt.

​
Set a team prompt

A team prompt defines team-wide rules. This can be used 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. Create Team Prompt Pn
  5. Create a new team prompt or modify the existing one.
  6. Click Save prompt.
The changes will be 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. This informs Bolt about the internal libraries. It also helps fill in any knowledge gaps about third-party packages where Bolt may have limited knowledge of the package or the 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. Add Package Instructions Pn
  5. Enter the exact package name as it appears in package.json. New Package Prompt Pn
  6. Enter your prompt and save.

​
Private NPM registries

You can integrate Bolt with any private NPM registry, only if they are 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. Add Private Registry Pn
  5. Click Add private registry.
  6. Fill in the URL, token, and the optional scopes. Registry Details Pn
  7. Save the new registry.
If you leave the scope field empty: All package installations for your team will run through your private registry. If you fill in the scope field: All package installations for the SELECTED SCOPE for your team will run through your private registry.
Bolt keeps registry credentials secure in your account settings. It does not create or update an .npmrc file. Team members need to manage their .npmrc files for local development.

​
Switch between personal and team accounts

Click the profile icon in the top left of your screen to switch between your personal and team accounts.

​
Copy personal projects to Teams

If you want to duplicate a personal project into a Teams plan, follow these steps.
This will create a copy of the project files; it will not 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.