Hospitality Private hotel workspaces
Each hotel operates through its own workspace. Application access and data requests are scoped to the authorised workspace.
Security & Trust
Security & Trust
Clear handovers. Reviewed procedures. Controlled access.
Handover + SOP helps hotel teams share operational information and maintain procedures in an authorised hotel workspace. This page explains the access controls, review responsibilities and pilot boundaries.
Last updated: 13 November 2026
How access is protected today
These protections concern handovers, SOP drafts, approved procedures, step images and captions.
Invitation-based access
Hotel users receive access through the approved onboarding or invitation process. Public demos do not grant access to private hotel records.
Secure account access
Users sign in through authenticated accounts. Protected workspace pages check access before displaying hotel information.
Database-level protection
Database access policies help prevent users from reading or changing information outside their authorised workspace.
Controlled operator access
Hotel workspace access and platform administration have separate permissions. Platform operator access is restricted; an ordinary hotel account does not grant platform administration rights.
Hotel-specific information
Handovers and procedures are associated with the relevant hotel. Staff create drafts; authorised managers review an exact revision before publication. Later draft edits do not overwrite that approved version.
Your team reviews the work.
Handover + SOP is in pilot. Staff must check generated handovers and review procedure steps, images and captions before approving or relying on them. Output can contain mistakes or omissions. The service does not replace hotel judgement, emergency procedures or authoritative records.
Built carefully as the platform grows
Before live pilot use, we agree the hotel’s authorised users, data-processing terms, permitted information and retention arrangements. The initial pilot excludes medical information and sensitive HR records. Use approved hotel systems for those records and urgent safety matters.
Common questions
Straightforward answers based on how Hospitality Flow works today.
Can another hotel access our workspace?
Hotel workspaces are designed to keep each hotel’s private records separate, using account permissions and database access controls. Checks with fictional hotel accounts have tested workspace separation and removal of access. Further checks of the deployed service remain before real hotel data is approved for the pilot. Report any unexpected access to hello@hospitalityflow.co.uk.
How does a user receive access?
Access is arranged personally for the pilot and requires an authenticated account with permission for the relevant hotel. Viewing a fictional demo does not create an account or grant hotel access.
What happens when someone opens a protected page without access?
Private workspace pages require authentication and the relevant hotel permissions. An unauthorised account must not receive private hotel information.
Does Hospitality Flow connect automatically to our PMS, email or WhatsApp?
No. Hospitality Flow does not connect to external hotel systems unless an integration is deliberately configured and authorised.
Is Hospitality Flow formally GDPR certified?
Hospitality Flow is being developed with responsible data handling in mind, but this page should not be interpreted as a formal compliance certification.
Questions about security or hotel data?
We are happy to explain how access and workspace separation currently work before a pilot begins.
This page describes the current Hospitality Flow platform and will be updated as security capabilities develop.