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.
-
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.
-
Assign a role: Diver, Surface support or Observer. Diver is the default.
-
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. |
| Diver | Role | TTS | Runtime | First stop | Status |
|---|---|---|---|---|---|
| Alex MoreauYouTX 21/35EAN50 | Owner | 34 min | 61 min | 21 m | Ready |
| Inés FerrerTeam planTX 21/35EAN50 | Buddy | 41 min | 68 min | 24 m | Ready |
| Sam Okonkwo | Buddy | Awaiting setup | |||
| Mei Tanaka | Surface support | Surface team |
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.
Next
Pairing a dive computer starts the dive log, and Roles and invites covers the permission model elsewhere in the app.