Publishing makes a solution live: its app becomes available to your users at its Application URL. Until you publish, changes stay in the builder's preview.
Overview
You publish from the Solution builder. Open the Preview tab and click Publish in the header. Publishing ships the whole solution — the app and every asset linked to it, at their current saved versions — not just the app.
Publishing uses the current saved version. Save any pending edits before publishing; unsaved changes are not included.
Publish is available once the app has its first build. It is disabled with "Can't publish right now — the app hosting service is unavailable" if your environment's app hosting service isn't running.
Publishing Step by Step
In the Solution builder, open Preview and click Publish.
Optionally enter a tag in Tag this version. If you leave it blank, the version is published under the next version number — the box shows it, for example V3.
Optionally add Version notes — "Add notes for the release" — to describe what changed.
Check the Access section, which shows the app's Application URL with a copy button.
Click Publish.
A version tag must start with a letter and can contain only letters, numbers, _ and - — no spaces or other special characters. A checklist shows the rules as you type, and Publish stays disabled until the tag is valid.
The bottom of the panel shows when the app was last published — for example "V2 Published 3 days ago" — or Not Published.
When Publish Is Unavailable
Up to date — nothing has changed since the last publish, so there's nothing new to publish. Any change by the agent, a code edit or a visual edit makes Publish available again.
"Publishing is unavailable while the agent is working" — wait for the Solution agent to finish, then publish.
Making the App Visible in Enterprise Brain
The Access section also has a Visible in Enterprise Brain toggle. Turn it on to make the app available through your organisation's Enterprise Brain package when you publish, then choose who can see it under Visibility:
Option | Who can see the app |
|---|---|
Everyone | Everyone in the Enterprise Brain package. |
Specific people | Only the people you choose. |
Teams | Members of the teams you choose. |
When you publish, the app is first moved into the Enterprise Brain package and shared with the people or teams you chose, and then published. If either step fails you'll see an error and the app isn't published, so you can fix it and try again.
Note: Once an app is in the Enterprise Brain package it stays there — the toggle shows as on and locked with "This app is already published in the Enterprise Brain". The package then manages the app's users, roles and permissions, so the solution's Settings tab points you to the package's settings instead. See Solution App Settings.
After You Publish
You'll see "Your solution has been published."
The Overview page's Status changes to Published · vn. See Solution Overview Page.
The new version appears on the solution's Versions page. See Solution Versions and Restore.
Publishing a large solution can take several minutes.
If Publishing Fails
You'll see "Couldn't publish the solution" with the reason. The most common one is "The app has build errors, so it can't be published. Fix them via the agent and try again." — open Preview, use Fix with Agent, and publish once the build succeeds. Publishing also needs the Deploy permission on AI Solutions.