Skip to main content
Personas are the companion identities behind Syni-powered experiences. Each persona defines how the assistant presents itself (its name, description, tone, safety mode, and behavioral rules) for a specific app in a project. Open them from the project sidebar: Personas. The page subtitle reads “Companion personas for syni-powered experiences in this project.”
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

TypeEditable?Source
defaultNo (read-only)Provided by the Synheart Syni service
customYes: create, edit, deleteCreated by you in this project
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:
Form fieldDescription
AppThe app this persona belongs to (required)
NameDisplay name (required)
Persona keyUnique key, e.g. my.coach.v1 (required, fixed after creation)
DescriptionWhat the persona is and how it behaves
ToneThe conversational tone
Safety modeEnabled by default; keeps responses within safety guardrails

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.
Rule fieldDescription
ConditionWhen the rule applies
ActionWhat the persona should do
DescriptionHuman-readable note
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.”
Default personas cannot be edited or deleted from the dashboard. Build a custom persona instead if you need different behavior.

How personas relate to Syni

Personas are the menu of identities; the per-app Syni settings decide which of them an app may use:
Project Personas  →  define companions (name, tone, rules)


App → Syni → Persona allowlist  →  restrict which personas this app may use
An empty allowlist on the Syni page means the app may use all project personas. To restrict an app to specific personas, select their keys there.

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.