> For the complete documentation index, see [llms.txt](https://helpdesk.smaply.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.smaply.app/personas/personas.md).

# Personas overview

Personas represent the customer types your journey maps are about. Assign them to cards, filter journeys by persona, and keep research connected to real archetypes.

New to personas? This walkthrough covers the whole workflow, from building a persona with live data to filtering your journey maps by it.

{% embed url="<https://www.youtube.com/watch?v=sorVbcQTg5k>" %}

Prefer to read? The guides below break it down step by step.

### Build personas

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><h4>Create a persona</h4></td><td>Create a persona, pick template cards, and fill in the core details.</td><td><a href="/pages/q92JEZ67HauDof23i4mL">/pages/q92JEZ67HauDof23i4mL</a></td><td><a href="/files/1TuZbdvr3NEsYrV6Pdqd">/files/1TuZbdvr3NEsYrV6Pdqd</a></td></tr><tr><td><h4>Edit a persona</h4></td><td>Change card content, the layout, the icon and colour, and the info panel.</td><td><a href="/pages/QSksmHh3bfnMcEMGSGYE">/pages/QSksmHh3bfnMcEMGSGYE</a></td><td><a href="/files/oahyRWdJxdTS1AKuXBqu">/files/oahyRWdJxdTS1AKuXBqu</a></td></tr><tr><td><h4>Manage personas</h4></td><td>Duplicate, archive, restore, delete, and bulk-edit personas from the list.</td><td><a href="/pages/oScEAxHrtqqY2twvz5kM">/pages/oScEAxHrtqqY2twvz5kM</a></td><td><a href="/files/TsiCUz7w3YzLC6YBgUIn">/files/TsiCUz7w3YzLC6YBgUIn</a></td></tr></tbody></table>

<br>

***

### Use personas on maps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><h4>Assign a persona to a card</h4></td><td>Mark which personas a card is relevant for, on any journey map.</td><td><a href="/pages/42b6nVolnvr4VE3kfJ6s">/pages/42b6nVolnvr4VE3kfJ6s</a></td><td><a href="/files/2J7w3u77DuYd2gC3FnM1">/files/2J7w3u77DuYd2gC3FnM1</a></td></tr><tr><td><h4>Filter map by personas</h4></td><td>Show one persona's content at a time on a journey map.</td><td><a href="/pages/zxwopszZeIAP89VtDjFI">/pages/zxwopszZeIAP89VtDjFI</a></td><td><a href="/files/vRGOt9dTWPwjQkgLFlUJ">/files/vRGOt9dTWPwjQkgLFlUJ</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdesk.smaply.app/personas/personas.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.