Lovable: Publish from Chat and Workspace View-Only Sharing

Publish Your App Without Leaving the Chat

Lovable's agent gained the ability to publish and deploy apps directly from within the chat interface. Previously, deploying a project required navigating to the Publish dialog as a separate action outside the conversational flow. Now, any natural-language request to deploy, such as "publish my app", "ship it", "go live", or "deploy to production", is handled end-to-end by the agent without interrupting the development session.

How Publishing from Chat Works

When the agent detects a publish request in the chat, it:

• Inspects the current publishing configuration and workspace permission settings
• Verifies that all required page information is in place
• Runs the same security validations used by the standard Publish dialog (including security scans for apps connected to Supabase)
• Requests user approval before deploying, unless auto-approve has been configured
• Supports specific subdomain requests (e.g., "publish to my-todos.lovable.app")

For actions outside the scope of chat-based publishing, such as connecting a custom domain, adjusting visibility settings, or unpublishing, the agent directs users to the appropriate section of the UI. Publishing from chat counts as standard chat usage and consumes credits like any other prompt.

This change reduces context-switching during active development cycles. Teams iterating rapidly on a project no longer need to interrupt their workflow to locate the Publish button; they can prompt, refine, and ship all within a single conversational session.

Workspace View-Only Sharing for Business and Enterprise

Business and Enterprise workspaces can now share projects with all workspace members in a read-only "Can view" mode, configured directly through the Share dialog. This expands on Lovable's existing viewer role (previously available only at the individual collaborator invitation level) by enabling workspace-wide view-only distribution in a single step.

Who This Is For

The feature is designed for teams where workspace members need access to a project for review or reference, but should not be able to introduce changes. Common use cases include:

• Distributing reference implementations or approved design system projects to the broader team
• Allowing stakeholders to inspect completed work before a handoff
• Letting non-builder team members (designers, product managers, QA reviewers) observe a project's current state without any edit risk

Workspace members granted "Can view" access can preview the build and leave comments, but cannot edit code, trigger a publish, or modify project settings. The editor role remains unchanged for active collaborators who need full build access.

Availability

Workspace view-only sharing is available on Business and Enterprise plans. Individual project-level viewer invitations (inviting a specific person by email with viewer access) remain available on paid plans across all tiers.