> 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.md). # Personas - [Personas overview](https://helpdesk.smaply.app/personas/personas.md): Create and use customer personas to ground journey maps in real user archetypes - [How to create a persona](https://helpdesk.smaply.app/personas/how-to-create-a-persona.md): Build a customer persona from a template, set its layout, and start filling in their story. - [How to edit a persona](https://helpdesk.smaply.app/personas/how-to-edit-a-persona.md): Change card content, add or remove cards, switch the layout, and set the icon, color, and details on an existing persona. - [How to assign a persona to a card](https://helpdesk.smaply.app/personas/how-to-assign-a-persona-to-a-card.md): Tag journey map cards with the personas they apply to, so the map shows whose experience each step belongs to. - [How to filter a journey map by persona](https://helpdesk.smaply.app/personas/how-to-filter-a-journey-map-by-persona.md): Narrow a journey map to one or more personas so the map shows only the cards relevant to them. - [How to manage personas](https://helpdesk.smaply.app/personas/how-to-manage-personas.md): Sort, duplicate, share, archive, and delete personas from the workspace Personas list, one at a time or in bulk. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://helpdesk.smaply.app/personas.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.