> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anyshift.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Personas

> Control how Annie communicates — its tone, depth, and assumptions — for different team members.

## Overview

Different team members need different things from Annie. An SRE wants terse, action-oriented answers. A CSM needs business-impact summaries. A junior engineer benefits from step-by-step explanations.

**Personas** let you control how Annie communicates by assigning behavioral profiles to team members. Each persona adjusts Annie's tone, depth, and assumptions without changing what it can do.

## Built-in Personas

Annie ships with four personas ready to use:

<AccordionGroup>
  <Accordion icon="terminal" title="SRE Annie (Default)">
    Conversational and direct. Assumes the user is a fellow SRE with deep technical knowledge. Provides brief answers, skips basic definitions, and suggests concrete next actions.

    Best for: **SREs, DevOps engineers, platform engineers**
  </Accordion>

  <Accordion icon="magnifying-glass" title="Evidence Annie">
    Focused exclusively on finding and presenting evidence. Cites every claim with specific data sources. Uses bullet points and structured data instead of prose. Does not speculate beyond what the evidence shows.

    Best for: **Incident investigations, compliance reviews, audit trails**
  </Accordion>

  <Accordion icon="chalkboard-teacher" title="Tutor Annie">
    Patient and thorough. Assumes the user is learning the system. Explains concepts step by step, defines technical terms, and provides context about why things work the way they do.

    Best for: **Junior engineers, new team members, onboarding**
  </Accordion>

  <Accordion icon="handshake" title="CSM Annie">
    Non-technical and business-focused. Translates technical details into business language. Focuses on who is affected, what the customer-facing symptoms are, and what the resolution status is.

    Best for: **Customer Success Managers, account managers, sales engineers**
  </Accordion>
</AccordionGroup>

## Custom Personas

Need something more specific? Create custom personas tailored to your team's unique roles and workflows.

Navigate to **Annie → Personas** in the sidebar to create custom personas with:

* **Label** — A short name (up to 50 characters), e.g. "Lean SRE" or "Sales Engineer"
* **Instruction** — Behavioral instructions for Annie (up to 1000 characters) describing the tone, depth, and assumptions to use

Custom personas appear alongside built-in ones in all persona selection dropdowns.

### Example Custom Personas

<AccordionGroup>
  <Accordion icon="gauge-high" title="Lean SRE">
    ```
    Focus on speed and actionability. Skip all context and explanation.
    Give me the shortest possible answer: what's broken, what metric
    confirms it, and what's the fix. One sentence per point. If you
    need to run a tool, just do it — don't ask permission.
    ```
  </Accordion>

  <Accordion icon="chart-line" title="Sales Engineer">
    ```
    Assist with pre-sales technical discussions. Frame infrastructure
    capabilities as business outcomes (uptime, cost savings, compliance).
    When reviewing incidents, emphasize MTTR and preventive measures.
    Keep language accessible to technical buyers — avoid deep CLI
    commands or config details unless asked.
    ```
  </Accordion>
</AccordionGroup>

## Assigning Personas

Personas are assigned per project in **Settings → Projects & Teams**:

* **Default persona** — Applied when a team member has no individual assignment, or when the user can't be identified (e.g., unlinked Slack users). Set this above the team members table.
* **Per-member persona** — Override the default for specific team members using the Persona column in the members table.

<Info>
  Members can change their own persona. Admins can change anyone's persona.
</Info>

### Slack Users

Annie identifies Slack users through the Slack user mapping. When a Slack user is linked to their Anyshift account, their assigned persona is applied automatically. Unlinked Slack users receive the project's default persona.

### Per-message override

Next to the chat input there is a **Persona** dropdown. Choosing a persona there applies it to that message only — it takes priority over your assigned persona and the project default. Leave it on **default** to use the persona assigned to you.

## Personas in Proactive Findings

Personas don't only shape conversations — they also set the voice of automated **[Proactive Findings](/pages/product/proactive_annie)**. The persona chosen for a project decides how the report's findings, risks, and recommendations are written: CSM Annie turns it into a business-focused summary, Evidence Annie into a terse, evidence-led one, and a custom persona into whatever voice you defined.

Set it from [**Proactive Findings**](https://app.anyshift.io/proactive) — the **Report persona** control lists every built-in and custom persona. The choice applies to the whole project's Proactive Findings; leave it unset to keep Annie's default voice.

<Note>
  This applies to **Proactive Findings only**. For [custom reports](/pages/product/reports), tone and framing are part of the report definition you author at creation time — not a persona.
</Note>

## Get Started

<CardGroup cols={2}>
  <Card title="Create Account" icon="user-plus" href="https://app.anyshift.io/">
    Sign up for Anyshift
  </Card>

  <Card title="Request Demo" icon="phone" href="https://calendly.com/roxane-fischer/30-zoom-meeting?back=1">
    See Personas in action
  </Card>
</CardGroup>