Accounts and access
Hotel IT manages who can sign in, from the IT view. The scope is deliberately narrow: accounts and systems, not what anyone said.
What IT can do
- Create staff accounts with a name, a department and a role, and issue each person their login code.
- Deactivate an account. History stays; sessions, devices and future routing are revoked at once.
- Pair the connector, store integration references, read system health.
- Set up zones and beacons for the Floor view, where the hotel uses it.
What IT cannot do
- Read requests, transcripts or guest messages.
- Change how requests are approved or routed. Those are the general manager's.
- Manage Harlow's own internal accounts, or widen its scope to another property.
Signing in
Each hotel has a short hotel code for the browser app. A person picks their name and enters their own login code. Codes are personal: the app says so on the sign-in screen, and the printed guide repeats it.
Leavers
Deactivate the account the day someone leaves. Any badge they connected keeps working for the next person who connects it; nothing on the badge belongs to the person.
Audit
Account changes, sign-ins and configuration changes are logged with who made them. Hotel IT's own actions are attributed to the named IT account, never to a shared credential. See security@tryharlow.com on the reporting page for anything that looks wrong.