Vessel oversight
Sees the wider vessel context and the access model prepared for the yacht.
Available
GlassBridge Crew Operations
Keep the people-aboard record explicit.
Record crew presence and operating assignments aboard the yacht, with a clear human editor and no claim that software has inferred who is present.
Manual recordPeople aboard are entered and maintained by an authorized human.
Operating assignmentsPresence and current responsibilities remain visible together.
Editor attributionChanges retain the authenticated editor responsible for the update.
No inferred trackingThe ledger is not automatic headcount or a man-overboard system.
Manual crew ledger
Presence, assignment and the human update in one record.
The ledger remains a local authoritative record while keeping nearby owner, service and operating workflows easy to reach.
Presence boundary: GlassBridge does not infer, track or certify who is aboard. The manual crew ledger is not a man-overboard system.
Roles across the yacht
One product language, responsibilities kept clear.
Roles explain who the experience is designed around; installation-specific access remains governed by the yacht's approved permissions.
Operating coordination
Coordinates assignments and reviews the manually maintained people-aboard record.
Guest experience
Prepares guest stays, rooms, presentation and the handling of guest requests.
Technical context
Relates engineering assignments to readiness, maintenance and energy workflows.
Assigned work
Works from operating assignments and guest requests routed to the crew inbox.
Prepared stay
Uses the time-bounded onboard experience published for the invitation.
Distinct guest role
Remains within the same time-bounded, stay-scoped access model.
Connected operating context
The ledger sits beside the work of running the yacht.
Crew Operations links people and assignments to the existing operating areas without pretending that navigation through the product is automatic presence evidence.
Owner & readiness
Owner context, daily readiness and voyage workflows remain close to the crew record.
Maintenance & energy
Maintenance, warranty, energy and technical-library areas support engineering follow-through.
Guest & support
Guest Experience, service coordination, notifications and support stay accessible from the operating surface.
Reports & timeline
Timeline, cost and reporting areas retain the wider vessel record around the crew workflow.
Three separate boundaries
Crew presence is not guest access or Cloud identity.
No access record, camera observation or network signal silently becomes a crew-presence fact.
Manual and local
The authoritative people-aboard entry records presence, assignment and editor attribution.
Invitation and stay
Time-bounded onboard access prepared for a guest visit, not a crew-presence record.
Review Guest Experience →Separate remote identity
Invitation-only, authenticated and read-only vessel monitoring with its own identity boundary.
Review Cloud access →Crew Operations planning
Start with the onboard roles and the record the team must maintain.
Crew Operations scope follows the yacht's operating structure, assignment model and approved permissions.