A solution's Settings tab controls the application generated from that solution: who can use the app, what they're allowed to do in it, and how they sign in. These settings are about the app's users, not about who can work on the solution itself.
Overview
Open the solution from the solutions list and select the Settings tab. It opens on Users, with a side menu of settings in two groups:
Group | Pages |
|---|---|
Governance | Users, Teams, Roles, Permissions |
Security | Privacy Settings, Content Security Policy, Password Policy |
To edit application settings, you need edit access to the application and the required global permissions. For standard managed applications, some add and edit actions may be unavailable.
Who can view, change, publish or delete the solution is controlled separately, by AI Solutions permissions. See Enabling AI Solutions and Access.
Before the App Is Built
Until the app exists, the Settings tab shows "Building your app" — "You'll be able to configure settings as soon as it's ready. Check the Overview tab for build progress."
Apps in Enterprise Brain
If you've made the app visible in Enterprise Brain when publishing, the package manages its users, roles and permissions. The Settings tab then shows Application Settings — "Application settings are determined by package level configurations." — with a Package Settings button that opens the package's own settings. See Publishing a Solution.
Governance
Page | What you can do |
|---|---|
Users | "Manage your application users." See the app's users, add users with Add Users, edit a user's details, roles and teams, and review the Activity tab. |
Teams | "Manage, view, set teams". Create teams with Add Team, then add users to a team directly or with User Criteria Match rules, and give the team roles. |
Roles | "Manage, view, set roles". Create roles with Add Role and set what each role can do across the Application, Platform, Connectors and Objects. |
Permissions | "Manage, view, set or update permissions here". Define the app's own named permissions and permission groups. |
Privacy Settings
"Choose who can access your app." Under Access level — "Controls who can open this application" — choose:
Private — "Only users you choose can access". You then manage the app's Identity providers — "Configure authentication methods" — turning each sign-in method on or off, or adding one with Add identity provider.
Public — "Anyone with the link can access".
Click Save to apply your changes.
Password Policy
"Configure authentication settings for your application." Set the rules for users who sign in with a password:
Password Length — a minimum and maximum between 8 and 64 characters.
Security Rules — require uppercase letters, lowercase letters, numbers and special characters, and block common passwords and personal information. All are on by default.
Password Lifecycle — Password Expiry in days, Minimum Password Age, and Prevent Password Reuse.
Click Save to apply your changes.
Content Security Policy
"Content Security Policy (CSP) helps protect your web app by controlling which external resources and content it can trust." Add URLs, each with a description, to two lists:
Resource Control — the outside sources the app may load resources from, such as third-party services or data sources.
Frame-ancestors — the websites allowed to show the app inside their own pages, for example as an embed.
Enter plain web addresses such as https://example.com, or 'self'. Each URL is checked as you add it.
Content Security Policy helps protect your web app by controlling which external resources it can load and which websites can embed it. Use the toggle to enable or disable CSP. When CSP is disabled, enable it before adding allowed sources or embedding sites.
Click Save to apply your changes. If any URLs aren't valid, fix them before saving.