Skip to main content

Permissions, Budget, and Personalization

These three settings live together in a project's dashboard settings because they're all "project behavior" knobs — distinct from the visual theming and branding settings covered in Customization.

Permissions​

A project's settings include project-wide defaults for what the agent is allowed to do: whether it can navigate, fill forms, interact with UI elements, and submit forms, plus allow/block lists for specific screens and actions.

This is the same AgentPermissions model documented at Concepts: Permissions and applied on the client at SDK: permissions. The dashboard sets the project-level baseline that applies across every app build using that project's API key; the SDK's own config is the setting for that particular client build. Exactly how the two combine is enforced server-side — from the dashboard's perspective, think of it as setting sensible defaults for the whole project, with the SDK able to further restrict what an individual build allows.

  1. Open your project in the dashboard.
  2. Go to its permissions settings.
  3. Toggle the navigate / fill forms / interact with UI / submit forms switches, and optionally add allowed or blocked screens and actions.
  4. Save. The new defaults apply to subsequent agent activity on that project.

Budget​

Budget settings let you cap usage on a project so a runaway conversation loop or an unexpectedly busy traffic period doesn't run up unbounded spend. Configure a limit or threshold for the project; as usage approaches or hits it, you'll see a warning, and requests beyond the limit may be blocked depending on how you've configured it.

See Usage and analytics for where you'd actually watch consumption against whatever budget you've set.

Personalization​

Personalization covers the assistant's name, avatar, welcome message, persona tone, default locale, and theme. The persona prompt is applied server-side; everything else is delivered to running apps automatically — the SDK fetches the project's personalization when it mounts and uses it as a fallback for any prop the app didn't set in code (explicit prop → dashboard → SDK default). Saving in the dashboard invalidates the server-side cache, so a change shows up on the app's next launch. The fields themselves are documented in the Customization section: Customization overview, Persona, Branding, Internationalization, and Theming — this page won't re-document them individually.

Next steps​

Last updated on