Invite with clear limits
Record the guest, start and end dates, assigned rooms, permission template, language and optional PIN. Current stays remain visible for review.
Available
GlassBridge Guest Experience
Prepare the stay before the guest steps aboard.
Invite each guest for a defined stay, shape what they can use and publish a calm onboard experience without exposing crew or engineering detail.
Time-bounded accessEvery invitation has an explicit start and end.
Stay-shaped permissionsRooms, permission template, language and optional PIN belong to the stay.
Preview before publishingContent, brand and guest view can be reviewed together.
Requests reach crewGuest requests are routed into the onboard crew inbox.
Guest Experience Studio
One place to prepare, publish and review the stay.
Stays, content, brand presentation and guest-view preview use one onboard product language.
From invitation to crew follow-through
Guest access stays attached to the visit.
The Studio keeps the invitation, published experience and service requests inside the onboard stay workflow.
Publish only what belongs
Prepare stay-scoped content, apply the yacht's guest brand and preview the guest view before it is used aboard.
Keep requests with the crew
Guest requests enter a crew inbox so onboard service remains part of the yacht's operating workflow.
Guest roles
A guest experience without a second crew system.
Guest and guest-child roles remain within the stay; the responsible onboard team prepares and follows the experience.
Stay-scoped onboard access
The invited guest receives the content and permissions prepared for that visit.
A distinct guest role
Guest Child remains inside the same time-bounded, stay-scoped model and the permission template selected for the invitation.
Prepared and followed aboard
Chief steward and crew workflows connect stay preparation with the guest-request inbox.
Three separate boundaries
Guest access is not crew presence or Cloud identity.
GlassBridge keeps each record responsible for one job and does not infer one from another.
Invitation and stay
Local, time-bounded access to the onboard experience prepared for the guest.
Manual people-aboard record
A separately maintained record of crew presence and operating assignments.
Review Crew Operations →Separate remote identity
Invitation-only, authenticated and read-only vessel monitoring; it does not inherit an onboard guest stay.
Review Cloud access →Guest Experience planning
Start with the stays, service standard and onboard roles.
Guest Experience scope follows the yacht's rooms, content, brand and approved permission templates.