---
title: Organise your team on the Team map
description: "Group colleagues into departments and teams, name managers and people who approve, set how much each colleague does alone, draw hand-off lines, and replay a run on the Team map."
new_in: "3.37"
---

The **Team map** shows how your company runs: your colleagues and routines,
the departments and teams they belong to, who hands work to whom, and who
approves it. It was called **How it runs**. Open it from **Team → Team map**.

The map doesn't create new colleagues or routines. It organises the ones you
already have and decides who approves their work.

## Before you start

Hire at least two colleagues and give each one clear job. Only the
workspace's owner or an admin names people as managers or approvers on a
team. A person who manages a team can change that team and the teams inside
it.

## Read the map

- A **colleague card** shows their name, role, their **level** (Ask, Approve
  or Auto) and the apps they work with. An app that isn't connected yet is
  marked, such as “HubSpot · not connected”.
- A **frame** is a department or a team. Teams sit inside their department,
  up to four levels deep.
- A **line** is a hand-off: work one colleague may pass to another. A manager
  line goes from a manager to their team.
- **What's happening** lists what is running and what waits for you, with
  **Approve** and **Not now**.

Moving a card or a frame changes only the layout, which is kept for the
whole team. Lines, teams and levels change how new work is handled.

## Make departments and teams

1. Under the map, in **Departments & teams**, choose **+ Department**, such as
   Sales or Tech.
2. Choose **+ Team** inside it. A team can also stand on its own.
3. Drag a colleague's card onto a frame to put them on that team. Drag them
   out of every frame to take them off. Each move says where they went, with
   **Undo**.
4. Move a frame by its label, with everything inside it, or resize it by its
   edges. **Tidy up** puts every card back in a neat grid.

## Name a manager and approvers { #name-a-manager-and-approvers }

Open a team's frame to see its panel. It saves as you go.

1. Under **Colleagues on this team**, choose **Make manager** beside one
   colleague. The manager splits the work they are handed among the team,
   hands the pieces down and checks what comes back before answering.
2. Under **People who approve**, add the people who decide what this team's
   colleagues ask before acting. With nobody named, the approvers of the team
   above decide, and at the top, you and the workspace's admins.
3. Set the team's limit: each colleague on it does at most this much alone,
   whatever their own level.

Nobody approves their own request. A person who approves can lower a
request's budget, never raise it.

## Choose how much a colleague does alone { #choose-how-much-a-colleague-does-alone }

Open a colleague's card and choose their level:

| Level | What it means |
|---|---|
| **Ask** | Asks before starting anything, routine work included. |
| **Approve** | Does routine work alone; anything else waits for a yes. |
| **Auto** | Does the work alone and tells you. Hiring and sending anything outside the company still ask. |

When their team allows less, the card says “Their team allows up to …”. To
move a colleague up with evidence first, give them an
[exam](exams.md).

## Draw a hand-off line

1. Switch to **Build**.
2. Draw a line from the colleague who spots the work to the colleague
   responsible for the next result.
3. Add an **Only when…** rule another person can test, such as “when the
   customer asks for a refund”.
4. Choose whether the hand-off runs automatically or asks first.
5. To change a line, open it: **Hands work to** points it at someone else,
   and **Stop** removes it.

## See a run

An answer that handed work to the team has **See the run** where it used to
show how long it worked. It opens the Team map and replays the run step by
step: who handed what to whom, what was asked and approved, the manager's
review, and what came back. Choose **Replay again** to watch it again.

You can also open any item under **What's happening** to light up its path.

## What happens next

New lines, teams and levels apply to new work. A run already going keeps the
route and approvals it started with. Work that waited on a team you change
goes to the owner and admins to decide.

## Tips

- Give every recurring result one owner.
- Start colleagues on **Ask**, and raise them after good results or a passed
  exam.
- Keep public-answer work apart from bookings, payments and account changes.
- Test one hand-off at a time before you build a longer chain.

## Troubleshooting

- **A colleague won't go on a team:** you need the right to change that
  colleague. Ask the person who hired them, or an owner or admin.
- **Work waits for someone unexpected:** open the waiting item; it names the
  team whose approvers decide it.
- **A line never runs:** check its direction, its **Only when…** rule, and
  that the receiving colleague is on.
- **A frame can't get smaller:** it never shrinks below what it holds. Move
  some cards out first.

## Related

[Hire and shape a colleague](colleagues.md) · [Approvals and control](control.md) ·
[Exams](exams.md) · [Missions](missions.md) · [Create and run a routine](routines.md)
