---
title: "Team plans"
description: "Invite divers to a plan, set what each of the four roles can do, and read the comparison that shows whose schedule the team is bound to."
---

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

# Team plans

import { TeamComparison } from "@/components/react/PlannerScreens";

A team plan is one dive and one schedule per diver: every member works from the
same profile, but each brings their own gases and decompression settings.

## The four roles

- **Owner**: everything below, plus setting the shared configuration, inviting
  and removing members, changing roles, and deleting the plan. Held by the
  plan's creator, with no way to hand it on.
- **Diver**: views the plan, edits its name and notes, enters their own gases
  and decompression settings, and gets their own schedule.
- **Surface support**: views the plan and the whole team's schedules. Enters no
  dive settings.
- **Observer**: views the plan. No team function.

Every role but Owner is set at invite, or later by the owner. Surface support
and Observer have identical permissions, differing only in what the comparison
calls them, *Surface team* against *Observing*.

The **shared configuration** is the owner's alone: the levels, which no member
can change, and the baseline settings. Each Diver adds their own gases and their
own overrides for algorithm, gradient factors and SAC rates; their schedule is
the shared levels computed with those.

## Inviting divers

Only the owner can invite. An invitation carries a role and arrives as an email
and, for an address with a DiveLogic account, an in-app notification.

1. **Search for the diver by email** under **Add team members**. Existing
   accounts appear with their name; an address with no account can be invited
   directly from the results list.

2. **Assign a role**: **Diver**, **Surface support** or **Observer**. Diver is
   the default.

3. **Confirm.** Nothing is shared until the invitation is accepted.

An invitation is *pending* until it is accepted, declined, revoked by the owner,
or **expires seven days** after it was sent. Accepting requires the account's
email to match the address it went to.

## The team comparison

The team view lists every member as one row:

| Column | Shows |
|---|---|
| **Diver** | Name, a **You** chip on your own row, and their gas mixes. |
| **Role** | Owner, Diver, Surface support or Observer. |
| **TTS** | Time to surface, in minutes. |
| **Runtime** | Total runtime, in minutes. |
| **First stop** | First decompression stop, in metres. |
| **Status** | *Ready*, *Awaiting setup*, *Surface team*, *Observing*, or the reason their plan failed to compute. |

The schedule columns appear only once the owner has set at least one level. One
row is marked **Team plan**: the member with the **longest TTS**, whose
obligation the rest of the team waits out. It weighs nothing else, not gas
reserves or CNS.

A **merged stop list** sits alongside the rows: every stop depth any member has,
at the longest duration any member holds it. It is not the longest member's
schedule, since a shorter-TTS diver can still have a stop nobody else does.

> **Caution**
>
> The comparison reports what the models produced. It does not endorse the longest
> schedule as the team's plan, or say whether the team should stay together. That
> is a briefing decision.

## Next

[Pairing a dive computer](/log/pairing) starts the dive log, and
[Roles and invites](/account/roles-and-invites) covers the permission model
elsewhere in the app.

Source: https://docs.divelogic.ai/planning/team-plans/index.mdx