> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vh3.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Teams

> Create dynamic ownership groups in VH3 Connect and assign them to Cases.

# Teams

Teams are the people who own a piece of operational work — a region, a customer portfolio, a service line, or a temporary incident room. They are not your company user directory.

**Path:** `/teams`

**Product roles** (Admin, Manager, Engineer…) control who can sign in and administer the company. That lives under [Users and roles](/connect/users-and-roles). **Teams** control who owns Cases and the customers or sites behind them.

Open **Teams** in the sidebar to create and manage membership. You also set **Assigned Team** on a Case.

## What a Team is for

| Team shape         | Example                            | Use it when                                           |
| ------------------ | ---------------------------------- | ----------------------------------------------------- |
| Operating patch    | North Region, London reactive      | Recurring work should land with the same coordinators |
| Customer portfolio | Key accounts, housing associations | Account risk, reviews, and Cases stay together        |
| Temporary room     | Berwyn House major incident        | You need a short-lived group around one problem       |
| Service focus      | HVAC response, lifts compliance    | Specialist signals and follow-through                 |

Create the grouping that matches the work in front of you. Close or deactivate temporary Teams when the work is done.

## Teams and Cases

Cases are the work containers. Teams are who the Case is assigned to.

1. A signal appears — sentinel, Connie investigation, email triage, or a search you ran yourself.
2. You [create a Case](/connect/cases) from the Cases page or from [Advanced search](/connect/search) and link the jobs, contacts, or sites that matter.
3. Assign an **Assigned Team** so the right ownership group sees it.
4. Add **participants** for people who need the Case but are not the owning Team.
5. Comment, update status and priority, and follow the activity timeline until it closes.

Connie can find Teams and Cases, annotate Cases, and set or clear Assigned Team. See [Ask Connie](/connect/ask-connie).

## Team membership vs product roles

| Concept              | Meaning                                                 | Where                                       |
| -------------------- | ------------------------------------------------------- | ------------------------------------------- |
| **Team role**        | Lead, member, observer (and similar) on a specific Team | Team membership                             |
| **Product role**     | Admin, Manager, Developer, Engineer, Standard           | [Users and roles](/connect/users-and-roles) |
| **Case participant** | Person on one Case without joining the Team             | Case **Participants** tab                   |

Someone can be Admin for the company, a `team_lead` on North Region, and a participant on a Case owned by another Team. Those are three different relationships.

## How to work this in Connect

1. Open **Teams** (`/teams`) to create the group and manage members.
2. Open **Cases**, find or create the Case that needs ownership, and set **Assigned Team**.
3. Add participants if individuals outside that Team need the thread.
4. Use comments for decisions and next actions; keep evidence on **Linked items**.
5. When Connie briefs a risk, ask her to open or update the Case and assign the Team — then review the timeline yourself.

For the full operating model (entity links, API shapes, agent handoffs): [Teams and cases](/guides/users-and-teams).

## Related

* [Cases](/connect/cases)
* [App overview](/connect/app-overview)
* [Search](/connect/search)
* [Ask Connie](/connect/ask-connie)
* [Users and roles](/connect/users-and-roles)
* [Teams API](/api-reference/teams)