Bolt.new Adds Team Collaboration Roles and Secure Private Domain Publishing

This shift mirrors a broader industry trend toward making AI-native development tools enterprise-ready. While early agentic tools focused on solo "vibe coding," professional adoption requires the security features found in traditional IDEs. This follows a pattern of team-based features appearing across the agentic landscape.
You can now share projects with individuals, teams, or via restricted links. The new publishing workflow allows for private deployments limited to trusted domains, protecting internal intellectual property. These features are available now, enabling you to manage complex development workflows and team-wide deployments more securely.
Frequently asked questions
- What are the new collaboration roles in Bolt.new?
- Bolt.new now features three distinct role-based access levels for project collaboration. Viewers can open and duplicate projects without making changes. Editors have the authority to prompt the AI and modify the code directly. Co-owners possess full administrative control over the project, including the ability to manage other collaborators and settings.
- How does private publishing work in Bolt.new?
- Publishing in Bolt.new is now a separate action from project sharing. Users can choose to publish their web applications publicly or keep them private. Private publishing allows creators to restrict access to specific trusted domains, ensuring that only users within a particular organization or group can view the deployed application.
- Who can I share my Bolt.new projects with?
- The rebuilt sharing infrastructure allows for flexible project distribution. You can invite specific individuals by email, share access with your entire team workspace, or generate a sharing link. These options allow for granular control over who can see or edit your AI-generated code, moving beyond simple public URL sharing.
- What is the difference between a Viewer and an Editor in Bolt.new?
- A Viewer in Bolt.new can access a project to see the code and duplicate it into their own account, but they cannot change the original project. An Editor has active permissions to interact with the AI agent, provide new prompts, and edit the codebase directly within the shared workspace.

