> For the complete documentation index, see [llms.txt](https://documentation.taskmaverick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.taskmaverick.com/your-organization/people/positions.md). # Positions A Position is a person's job title — like Chef, Receptionist, or Shift Supervisor. Positions form a hierarchy that mirrors your real organizational structure. {% hint style="info" %} **Position ≠ Role.** A [Role](/your-organization/people.md#roles) (System Admin, Org Manager, Employee) controls what someone can *do* in the system. A Position describes their *job*. {% endhint %} ## Why set up Positions? * **Control content visibility** — restrict [Media training](/missions/how-to-guides/configure-mission-settings.md#media-specific) to specific positions (e.g. only managers see "Leadership Training") * **Show context on mobile** — when someone requests a Mission, their position appears on the card so the team knows who's asking * **Filter reports** — analyze Mission completion by job title ## How to create a Position 1. Go to **People → Positions** tab 2. Click **New Position** 3. Enter: position name, optional tag, parent position (if any) 4. Save You can also right-click any position to **Add Parent** or **Add Child** to build the hierarchy visually. {% embed url="" %} {% hint style="warning" %} Every new organization starts with a default "Staff" position. {% endhint %} ## Good to know * The Position field is **required** when creating a person * Positions are hierarchical — each can have a parent and children, with no limit on levels --- # 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://documentation.taskmaverick.com/your-organization/people/positions.md?ask=&goal= ``` `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.