AI Solutions is turned on per environment and protected by its own set of permissions. This page explains how an administrator switches it on and what each permission lets people do.
Overview
Two things decide whether someone can use AI Solutions: the AI Solutions feature flag, which an administrator switches on for the environment, and the person's AI Solutions permissions, which come from their role. The side navigation entry appears only when both allow it.
Turning On AI Solutions
AI Solutions is off by default in every environment. To switch it on:
Go to Settings and open Feature Flags — "Turn platform capabilities on or off. Changes apply immediately and are recorded in each flag's history."
In the AI Assisted group, find AI Solutions ("One problem statement, one linked set of assets.").
Turn it on. The change applies immediately for everyone on the platform.
The flag's panel also shows a Planner model setting — "Plans the solution before it is built. Makers never see this choice." This is the model the Solution agent uses to plan solutions in this environment.
Once the flag is on, AI Solutions appears in the side navigation for everyone who has permission to view solutions.
Permissions
AI Solutions has its own permission set. Out of the box, only the Owner and Admin roles have these permissions; any other role needs them granted explicitly, starting with View.
Permission | What it allows |
|---|---|
View | See AI Solutions in the side navigation, open the solutions list, a solution's details pages and its builder, and read its plan and assets. |
Create | See the New solution button and create solutions. |
Edit | Rename a solution, edit its details and tags, and use the visual Edit mode on the app preview. |
Delete | Delete a solution. |
Share | Reserved for sharing solutions with others. |
Deploy | Publish a solution. A publish attempt without this permission is refused. |
What Viewers Can Do
Viewing a solution is deliberately generous: anyone with View can open the builder, read the plan and conversation they have access to, and look at the app, objects and workflows. Changes are blocked asset by asset — for example, a viewer without Edit sees the Preview's Edit mode locked with "You need edit access to change this app", and editing an object's records or schema depends on the person's permissions on that object.
Chats are private: each person sees their own conversations with the Solution agent about a solution. See Solution Chats and History.
When You Don't Have Access
No View or Create permission: instead of the page, you see "Access Denied: Permission Required" — "You don't have access to … yet." Write a note in "Let … know why you need access…" and click Send Request to ask the owner (or an admin) for access.
A solution that doesn't exist or can't be read: you see "No solution found" — "This solution may have been deleted or is no longer available." — with a Back to home button.
Sharing Solutions
Sharing a solution with other people from the solutions list is not available at the moment. Access that was granted earlier keeps working. To give people access to the app a solution builds, use the app's own settings — see Solution App Settings — or the Visible in Enterprise Brain option when you publish. See Publishing a Solution.