> 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/groups.md). # Groups A Group is a collection of people assembled for a specific purpose — receiving certification reminders, getting automated report subscriptions, accessing restricted Folders, or being assigned Courses. Unlike [Teams ](/your-organization/teams.md)(which are tied to locations and daily operations), Groups cut across your organization and serve administrative and communication needs. ## Why use Groups? Teams answer "who works together at this location." Groups answer "who needs to receive this notification, this report, or this training — regardless of where they work." **Example:** A hotel chain needs to send a monthly compliance report to all General Managers across 20 locations. Creating a "General Managers" Group lets you set up one report subscription that reaches all of them — without manually selecting 20 people every time. ## How to create a Group Go to **Group → New Group**. {% embed url="" %} ### Required fields | Field | Required | Details | | --------------- | -------- | ----------------------------------- | | **Name** | Yes | Unique group name | | **Tag** | No | For organizing and filtering Groups | | **Category** | Yes | For classification | | **Description** | No | Explain the Group's purpose | ### Adding people with Configurators Instead of picking people one by one, you define **who should be in the Group** using filters. Each set of filters is called a **Configurator**. 1. In the Group Builder, open the Configurator (Edit mode) 2. Set filters to narrow down your people | Filter category | Available filters | | ------------------------------------------------------- | ----------------------------------------------------------------------- | | [**Unit**](/your-organization/units.md) | State, County, City, Location, Building, Area, or specific Unit | | [**Team**](/your-organization/teams.md) | Division, or specific Team | | [**Ticket Board**](/your-organization/ticket-boards.md) | Board type, or specific Ticket Board | | [**People**](/your-organization/people.md) | Role, Position, Tags, Pay Type, State, County, City, or specific People | 3. The people table updates live as you adjust filters. You see exactly who will be included. 4. Click **Save** to assign those people to the Configurator By default, all filters are set to "All" — meaning everyone in the organization. Change only the filters that matter for your Group. ### Multiple Configurators A single Group can have **multiple Configurators** — each with its own filter criteria. This is useful when your Group needs people who match different conditions. **Example:** A "Safety Training Recipients" Group has two Configurators: one selecting all Kitchen staff across all locations, another selecting all Warehouse staff. Together, they populate the Group with everyone who needs safety training — without overlap issues (a person can belong to the Group through multiple Configurators). Switch to **View mode** to see a summary showing only the filters you changed (filters left at "All" are hidden). Click the people counter next to a Configurator name to see which people came from that specific Configurator. ### Quick creation from People table You can also create a Group directly from the [People ](/your-organization/people.md)table using **Bulk Selection**: select people with checkboxes → click **Create Group**. See [Shortcuts and Useful Actions](/missions/how-to-guides/shortcuts-and-useful-actions.md#bulk-create-a-group) for details. ## Managing Groups
ActionWhat it does
OpenView the Group Builder with all Configurators and people
DuplicateCopy the Group's configuration (name must be changed)
DeactivateTemporarily disable the Group — it stops receiving subscriptions and notifications
ActivateRe-enable a deactivated Group
DeletePermanently remove the Group
All actions are available from the context menu, navigation menu, and sidebar. ### Group sidebar Click a Group row to open the sidebar with three tabs: | Tab | What it shows | | -------------------- | ------------------------------------------------------ | | **Info** | Name, description, status, tags, category | | **People Selection** | Summary of all Configurators and their filter criteria | | **People** | List of all people currently in the Group | ## Where Groups are used
FeatureHow Groups are used
Report SubscriptionsSend automated reports to all Group members via email
CertificationNotify Group members about expiring certifications, assign Certifications to Groups
CoursesSchedule training Courses for an entire Group
FoldersGrant Folder access to a Group instead of individual people
Mission restrictionsRestrict On Demand or Knowledge Base access by Group
## Good to know * Groups are managed on the **web only** — not configurable from mobile * A person can belong to **multiple Groups** simultaneously * A person can appear in a Group through **multiple Configurators** — they're counted once * Configurator filters are **not interdependent** — changing one filter doesn't restrict the options in another * Deactivating a Group stops all subscriptions and notifications, but preserves the configuration * Only **System Admins** can create and manage Groups --- # 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/groups.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.