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

# Key concepts

> The shared data model — products, organizations, ships, crew, roles, training, and records

Seamind's products sit on top of one shared data model. Understand these concepts once and they carry across the whole platform.

## Products and pillars

Seamind OS is organized into **products** grouped by **intelligence pillar**. Each organization has access to the products in its plan. Some data is shared across every product — organizations, ships, and people — while other data is product-specific, like courses (Learn) or certificates (Crew).

See [the product suite](/product-pillars) for what each product does and its current status.

## Shared resources

These exist at the platform level and are available to every product.

### Organization

Your organization is the top-level container for everything in Seamind — ships, people, training, and records. It's created when your company onboards, and all access is scoped to it.

### Ships

Ships represent the vessels in your fleet. Each ship carries identifying details:

* A **name** (e.g. "MV Pacific Voyager")
* An **IMO number** — the unique 7-digit identifier assigned by the International Maritime Organization
* Optional registry details — **MMSI**, **call sign**, **flag**, and **port of registry**

Ships are used across products — in Learn for training assignments, and in Crew for assignment history.

### People and roles

The people in your organization are **not** created manually in Seamind — they sync automatically from your identity provider (Okta, Microsoft Entra ID, Google Workspace) through SSO and directory sync.

Each person has a **role**, set in your identity provider, that determines what they can do:

| Role                | Who they are        | What they can do                                          |
| ------------------- | ------------------- | --------------------------------------------------------- |
| **Admin**           | Org owners / IT     | Everything, including SSO, directory sync, and user roles |
| **Office Admin**    | Senior office staff | Manage crew, assignments, programs, and verification      |
| **Office Employee** | Office staff        | Read fleet-wide data, create assignments, review crew     |
| **Crew Member**     | Seafarers           | Complete their own training, manage their own profile     |

Each person also has a **status** — Active, Pending, or Suspended — reflecting their state in your identity provider.

<Note>
  "Crew" means two related things in Seamind: the **people** in your organization (above), and the **Crew product** — the digital records those people own. The rest of this page covers the data each product adds on top of these shared resources.
</Note>

## Learn: training

These concepts power [Seamind Learn](/learn).

```
Organization
├── Ships ────────────── your fleet
├── People ───────────── synced from SSO
├── Courses ──────────── individual training modules
├── Programs ─────────── named groups of courses
└── Assignments ──────── person + ship + role + dates
    └── Registrations ── one person's progress on one course
```

### Assignments

An assignment places a crew member on a specific ship. It captures:

| Field             | What it means                                                   |
| ----------------- | --------------------------------------------------------------- |
| **Crew member**   | Who is assigned                                                 |
| **Ship**          | Which vessel                                                    |
| **Role on ship**  | Their seafarer rank (Captain, First Officer, Chief Engineer, …) |
| **Sign on date**  | When they board                                                 |
| **Sign off date** | When they leave                                                 |
| **Due date**      | Deadline for completing assigned training                       |

Training is assigned to crew **through** their assignments — "this person, on this ship, during this voyage" — which is what makes Seamind maritime-specific rather than a generic course tool.

### Courses

A course is a single training module: a set of **slides** (the learning content) plus a **quiz** to assess understanding. Courses are the building blocks of all training. They can be assigned individually or grouped into programs.

### Programs

A program is a named collection of courses that forms a curriculum — for example "Maritime Safety Fundamentals" or "New Joiner Training". Assigning a program adds all of its courses at once.

<Note>
  Deleting a program does **not** delete the courses inside it, and courses already assigned through a program stay assigned.
</Note>

### Registrations

A registration is one person's progress on one course, created automatically when a course is assigned. It tracks **status** (Not Started, In Progress, Completed, Failed), **score**, **attempts**, **time spent**, and **completion date**. Each row on the admin Progress page is a registration.

## Crew: professional records

These concepts power [Seamind Crew](/crew) — the digital record each seafarer owns.

| Concept                | What it is                                                                    |
| ---------------------- | ----------------------------------------------------------------------------- |
| **Crew profile**       | Personal details, contact info, and next-of-kin for a seafarer                |
| **Identity documents** | Passport, visa, seaman's book, national ID — uploaded and tracked with expiry |
| **Certificates**       | Professional credentials (STCW, GMDSS, medical, flag, …) with expiry dates    |
| **Experience**         | Past employment history — ships, ranks, and dates                             |
| **Verification**       | The office's confirmation that an uploaded document or certificate is genuine |

A profile rolls up to one of four **verification states** — **Incomplete · In Review · Action Needed · Approved** — that tells everyone whose turn it is to act. See [Verification status](/crew/verification-status).