---
title: "Roles and invites"
description: "The four roles on a shared dive plan, what each one may do, and how an invitation is issued, accepted, declined or revoked."
---

> 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.

# Roles and invites

import { InviteDialog } from "@/components/react/ModalScreens";

A role is the permission one diver holds on one shared plan. Every plan has
exactly one owner and any number of other members.

## The four roles

| Role | What the app says it does | What it may change |
|---|---|---|
| **Owner** | The diver who created the plan | Everything: the shared dive configuration, other members' roles, invitations, and the plan itself |
| **Diver** | "Dives the plan and sets their own gases" | The plan, and their own per-diver settings |
| **Surface support** | "Follows the plan from the surface — view only" | Nothing |
| **Observer** | "Views the plan — no team function" | Nothing |

Everyone on the plan can read it, read the team and read their own settings. A
diver and the owner can edit the plan and write their own per-diver settings:
which gases they are carrying, and the numbers that follow. Only the owner
changes the shared configuration, which is the dive itself: its depths, its
environment, the settings every member's schedule is computed against.

Surface support and observer are equal in permission and differ only in team
function. Ownership is not a role you can be given, so a plan cannot change
hands by invitation.

## How an invitation works

The owner invites by **email address**, from a modal titled **Invite Divers**
with a search field labelled *Add team members*. The diver accepting must be
signed in as the address it was sent to.

An invitation carries the role it was issued with, so the owner decides at the
point of inviting whether someone is diving, supporting or watching. The role
can be changed afterwards by the owner.

The invited diver sees a notification titled *…invited you*, naming the plan and
the role, with **Accept** and **Decline** on the row itself, and the plan opens
as soon as it is accepted. There is no link to find and no code to paste. The
owner is notified in turn, whichever way it went, and again if a member later
leaves.

## Watch for

- **An invitation is good for 7 days.** Only one pending invitation can exist
  for a given address on a given plan, and the owner can revoke it.
- **A role governs one plan.** Being a diver on someone's plan gives you no view
  of their other plans, their dive log or their post-dive reviews. A course is
  the one membership that shares dive data.
- **A role says nothing about competence.** The app enforces who may edit a
  field; it cannot check that the person editing it is qualified to.

## Next

- [Team plans](/planning/team-plans) gives the procedure: inviting, per-diver
  gases, and reading the team comparison.
- [Courses](/account/courses) is the other membership model.

Source: https://docs.divelogic.ai/account/roles-and-invites/index.mdx