> 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/ticket-boards.md). # Ticket Boards Ticket Boards are where automated alerts ([Tickets](/missions/what-are-missions/ticket.md)) land when they're triggered. They route workplace issues — from broken equipment to HR incidents — to the right group of people for resolution. *** ## Why set up Ticket Boards? When an employee reports a problem through a [Mission ](/missions/what-are-missions.md)(e.g. answers "Yes" to "Were you injured?"), the system needs to know *where to send the alert*. Ticket Boards are that destination. Without one, triggered Tickets have nowhere to go. There are two types, each serving a different purpose: | Type | Handles | Example | | ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- | -------------------------------------------------- | | [**Unit Ticket Board**](/your-organization/ticket-boards.md#unit-ticket-boards) | Location-specific operational issues — broken equipment, low stock, maintenance | "The fryer in Kitchen at Downtown Store is broken" | | [**Organization Ticket Board**](/your-organization/ticket-boards.md#organization-ticket-boards) | Sensitive or company-wide issues — HR, harassment, compliance | "An employee reported discrimination" | The distinction exists to **prevent conflicts of interest**. A harassment report from a location shouldn't be routed to managers at that same location — it goes to a dedicated Organization Ticket Board handled by HR. *** ## How to set up Ticket Boards ### Unit Ticket Boards You don't create these — they're **automatic**. When you create a [Unit](/your-organization/units.md), its Ticket Board is created alongside it. It inherits the unit's name, address, and time zone. To manage it: go to **Ticket Boards** on the web → find the Unit Ticket Board → add or remove **People** (the only thing you can edit here). To change the board's name or address, update the Unit itself. ### Organization Ticket Boards These you create manually: 1. Go to **Ticket Boards → Organization Ticket Board → New Ticket Board** 2. Enter a **name** (e.g. "HR — Harassment", "Safety Incidents") 3. Enter a **physical address** (state, county, city) — this sets the time zone automatically 4. Save 5. Add at least one active person to **activate** the board {% embed url="" %} ### Managing Organization Ticket Boards
ActionHow
ActivateAdd at least one active person, or use Actions → Activate
DeactivateActions → Deactivate (only if no open Tickets and not set as a destination)
DeleteDeactivate first, then Actions → Delete Ticket Board
### Assigning people People on a Ticket Board are responsible for reviewing and resolving Tickets sent there. To assign: * Go to **People** → select a person → **Ticket Boards** tab → select boards * Or open the Ticket Board itself → **People** tab → add people On mobile, assigned users can access their Ticket Boards from: [Personal Board](/mobile-app/your-mobile-boards.md#personal-board) → Tickets, Organization view → Tickets, or [Unit Board](/mobile-app/your-mobile-boards.md#unit-board) → Tickets *** ## Good to know * An Organization Ticket Board **cannot be deactivated** if it has open/claimed Tickets or is set as a [destination](/missions/how-to-guides/configure-mission-settings.md#ticket-specific) for active Tickets * If the board is part of a [Process](/processes/what-are-processes.md), deactivating it will break the Process — the system shows a warning * Unit Ticket Boards **work even without people assigned** (marked as "Incomplete" until you add someone) — this supports opening new locations where staff haven't been assigned yet * The physical address determines the **time zone** for ticket timestamps and reporting. The ZIP code does not affect the time zone. * Any user in the Organization can be added to any Ticket Board — they don't need to belong to that location * Ticket Boards at different levels of a location hierarchy ([Unit → Building → Area](/your-organization/units.md#unit-hierarchy)) are **independent** — they don't inherit from each other * Every new Organization gets a **default Organization Ticket Board** automatically, with the System Admin added as a member --- # 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/ticket-boards.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.