> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/platform/teams.md).

# Teams

Represent your organizational structure within Pylon to set up workflows and automations

Create teams with assignment rules, then utilize them to set up targeted issue views and workflows, and analyze metrics relevant to different teams.

## Setup <a href="#create-teams" id="create-teams"></a>

### Team Creation <a href="#create-teams" id="create-teams"></a>

Create teams from the [teams page](https://app.usepylon.com/settings/teams/management) and add members.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FtRvOfhHtUOb4IJXIDbUn%2FCleanShot%202025-03-15%20at%2012.47.49%402x.png?alt=media&amp;token=9c557fde-9221-4132-af0e-99ae7cde917f" alt=""><figcaption></figcaption></figure>

Teams can also contain other teams as subteams. For example, you may have a broad Support team with different subteams representing various geographic regions.

## Usage

Teams can be used across Pylon as a filter value in views, triggers, macros, and more. Issues can also be assigned to a team manually from the UI, via the API, or via triggers and macros with the "Set issue team" action.

You can also set up complex [assignment rules](/pylon-docs/support-workflows/assignment-rules.md) to define behavior for what happens when an issue is assigned to a specific team.

## Staffing Heatmaps&#x20;

Forecast workload and optimize scheduling using live heatmaps of agent activity, handle time, and ticket volume.&#x20;

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FiN40v6CpKhWj5rPZJliW%2FCleanShot%202025-10-21%20at%2014.39.54.png?alt=media&amp;token=d6906289-5dc4-41ac-a305-69eac31e4ef4" alt="" width="563"><figcaption></figcaption></figure>


---

# 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.usepylon.com/pylon-docs/platform/teams.md?ask=<question>&goal=<user_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.