Agent Personas & Identity
Every Portal One agent can have a persona — a structured definition of who the agent is, how it communicates, and what it's expert at. Personas go beyond system prompts to give your agents consistent identity and behavior.
What's in a Persona
A persona defines your agent's:
- Identity — name, role, area of expertise
- Communication style — formal, casual, technical, friendly
- Behavioral guidelines — what to do, what to avoid, how to handle edge cases
- Expertise domains — subjects the agent should be knowledgeable about
Configuring a Persona
- Navigate to your agent's settings page
- Find the Persona card (collapsible)
- Write your persona definition in the text area
- Save — the persona is immediately active
The persona card shows a summary preview when collapsed, so you can quickly see each agent's identity at a glance.
How Personas Are Used
The persona is injected into the agent's system prompt at the beginning of every conversation. This means:
- The agent consistently maintains its defined identity
- Communication style stays on-brand across all interactions
- Behavioral guidelines are always in context
Tips for Writing Effective Personas
- Be specific — "You are a senior DevOps engineer who specializes in Kubernetes" beats "You are helpful"
- Define boundaries — tell the agent what it should NOT do, not just what it should
- Set communication tone — "Respond concisely with code examples" or "Explain concepts step by step for beginners"
- Include domain context — mention specific tools, frameworks, or conventions the agent should know about