Personas are configured at the project level and bound to an app. Which personas an app may actually use is controlled per app under Syni → Persona allowlist.
Persona types
Default personas always exist so an app has something to fall back on; you build custom personas to tailor the experience.
The personas list
Personas appear as cards with a count header and a Refresh action. Each card shows the persona’s name, a type badge (default or custom), a Safety on badge when safety mode is enabled, the unique key in monospace, its description, and its tone. Edit and Delete appear only on custom personas. If the project has no apps yet, the create modal shows “No apps in this project. Create an app first.”Create a persona
Click Create persona and complete the modal:Behavioral rules
Optionally add Rules; each rule has a Condition, an Action, and a Description. Use Add rule to add more and Remove to drop one. Empty rules are discarded on save.Persona behavior is expressed through description, tone, and rules. The dashboard does not expose a raw system prompt, voice, or avatar; those are not part of the persona model today.
Edit and delete
- Edit: change any field except the persona key, which stays read-only. Editing requires the persona’s app to be known (it’s selected automatically for app-bound personas).
- Delete: “Delete "" ()? This cannot be undone.”
How personas relate to Syni
Personas are the menu of identities; the per-app Syni settings decide which of them an app may use:Next
Syni
Enable Syni per app, set the execution mode, and restrict the persona allowlist.
App policy
The
Allow Syni flag that gates Syni access for an app.Consent profiles
Offer Syni as a consent option to end users.