> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/command/the-portal/personas.md). # Personas Reference for personas, the role-tailored workspaces that decide which content types and views each Command user is offered. A persona is a role-tailored view of one shared source of truth. An application owner and a CFO open the same instance and read the same records, but each sees a workspace built for their job. Personas change what is offered, never what is allowed. ## What it is Personas are configured in your instance. Command does not ship a fixed list of built-in personas. | A persona controls | How | | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | **The create menu** | It carries a set of content types, grouped into their categories. A persona given only Table, Roadmap and Note produces a create menu with three entries. | | **The activity rail** | It can carry all workspace views, a subset, or none, in which case the rail is empty. | | **Availability** | It is open to everyone, or restricted to named users and groups. Group members get it the same way as people named directly. | | **Identity** | It has a name, an icon and an accent colour, so it is obvious which one is active. | | A persona does not control | What does instead | | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Which records and fields you can read | ServiceNow roles and access rules. See [Access Rights](/command/prior-v26.0/configuration/access-rights.md) and [Roles & Groups](/command/prior-v26.0/configuration/roles-groups.md). | | Your saved content | Switching persona never moves, hides or changes anything in My Space. | | How an assistant answer is written | The assistant adapts an answer to its audience independently of your persona. See [Command Dialog](/command/features/command-dialog.md). | ## When to use it * **As a user**, pick the persona that matches the work you are doing today. * **As an administrator**, create personas to make the right work easy to find. Use roles and access rules to decide what people may see. ## How to ### Choose your persona 1. Click your **avatar** at the right end of the top bar. 2. Under **Working as**, click a persona. 3. Click anywhere outside the menu to close it. Command remembers your choice for the next visit. If you see only one persona, or none, your administrator has not assigned others to you.
The profile menu open with the Working as list of personas and the Command roles below it.

Switch persona under Working as

### Configure a persona (administrators) Personas are administered in the app, under **Global Settings > Persona**, and stored in your instance like any other configuration record. For each persona, set: 1. the name, icon and accent; 2. the content types it offers, and their order; 3. the workspace views it carries; 4. whether it is available to everyone, or to named users and groups. ## Good to know {% hint style="info" %} A content type that is switched off instance-wide does not appear in any persona. A persona whose content types have all been switched off has nothing to offer and is not shown as a choice. {% endhint %} * Removing a content type from a persona does not stop someone reaching the same data another way. * Your persona also decides which [Home](/command/the-portal/portal.md#home) sections you see. ## Related * [The Portal](/command/the-portal/portal.md) * [Content types](/command/the-portal/content-types.md) * [Access Rights](/command/prior-v26.0/configuration/access-rights.md) --- # 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://docs.ins-pi.com/command/the-portal/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.