Permissions

Every role. Right access.

A deckhand doesn't see finance. A department head can't approve their own expenses. An external surveyor sees only what you grant, for as long as you grant it.

Most yacht software gives you two options: admin or user.

That works until the owner wants financial visibility but shouldn't see crew personal documents. Until the chief stewardess needs provisioning access but shouldn't approve engineering purchases. Until a shore surveyor needs temporary access to safety records but nothing else.

YOS maps permissions to the natural chain of command on board — from owner to deckhand. When something needs to change, the captain changes it from Settings. No vendor call required.

Chain of command

Five levels. One system.

Owner & Management

Financial oversight and operational visibility across one or multiple yachts. Read-only where it matters.

Captain

Full operational command. Approves expenses, signs logbooks, manages crew, configures permissions.

Department Heads

Chief Engineer, Chief Stewardess, Chef — full control within their department, cross-department visibility.

Crew

Officers, engineers, stewardesses — access scoped to their responsibilities and assigned tasks.

External & Contractors

Surveyors, management staff, contractors — scoped, time-limited access with full audit trail.

Module access

Same system. Different data.

Every crew member logs into the same application. What they see depends entirely on their role.

Module	Captain	HOD	Crew	External
Finance	Full	Dept	Own	—
Maintenance	Full	Full	Tasks	View
Safety & ISM	Full	Full	Join	View

Showing 3 of 40+ modules. Full permission model covers every department on board.

Real scenarios

Built for how yachts actually work

Owner reviews budget status without seeing crew payroll details

Chief Stewardess manages provisioning but cannot approve engineering purchases

Shore surveyor gets 48-hour read access to safety records — nothing else

Junior crew submits personal expense claims but sees no other financial data

Department head approves team expenses but cannot approve their own

Security principles

Denied by default

Every permission starts at zero. Access is explicitly granted per role, per module. If it's not granted, it doesn't exist.

Full audit trail

Permission changes, data access, approvals — everything is logged with who, what, when. Complete accountability.

Captain-managed

Permissions are adjusted directly in Settings by the captain. No vendor call, no support ticket, no waiting.

Vessel-level isolation

Every data request is bound to a vessel identity. One yacht's crew cannot access another yacht's data.

See how it works with real data

Request a demo and log in as different crew members to see the same yacht from different perspectives.

Request a Demo See All Modules