# Teams

The **Teams** view helps you organize work by team instead of by individual person.

Open it from the left sidebar by clicking **Teams**.

## What you can do from the Teams page

The main Teams page separates the workspace into:

* **My teams:** Teams you belong to
* **All teams:** Other teams in the workspace

You can also:

* search for teams by name
* create a new team
* open a team page to inspect members, plans, and progress

## Open a team page

Click any team to open its detail page.

Each team page includes:

* **About this team:** A short description of the team's purpose
* **Team members:** The people currently assigned to the team
* **Team stats:** Aggregate progress across the team's outcomes and initiatives
* **Plans:** Plans attached to that team

The team header also links directly into filtered workspace views for that team's:

* objectives
* outcomes or key results
* initiatives

Depending on your workspace permissions and plan, you may also be able to edit the team color or delete the team from the team page.

## Why teams use Teams

The Teams view is helpful when your workspace has multiple departments, squads, or functions and you want a clear owner structure around execution.

Use it to:

* understand which plans belong to which teams
* review team-level workload before creating new goals
* see who belongs to each team
* jump from a team into filtered lists of its objectives, outcomes, or initiatives

## Related views

* [People](/docs/become-a-tability-power-user/features/people.md) helps you inspect work person by person
* [My focus](/docs/become-a-tability-power-user/features/my-focus.md) is the best view for managing your own updates
* [Adding more teams to your OKR process](/docs/become-a-tability-power-user/how-tos/adding-more-teams-to-your-okr-process.md) explains how to structure teams in a larger rollout


---

# Agent Instructions: 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:

```
GET https://guides.tability.io/docs/become-a-tability-power-user/features/teams.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.