Single sign on and directory sync hotel case: one signs operators into back office tools, one moves entitlements to doors, and each fails its own way.

Geplaatst op: okt. 27, 2025

Single Sign on and Directory Sync for a Hotel Property

Single Sign on and Directory Sync for a Hotel Property

The request that opened this single sign on and directory sync hotel case arrived as one sentence: staff should sign in once, and the doors should follow. The building already held a staff directory, a property system with guest stays, and an access platform with door rights, and the request assumed one identity flow could drive all three.

Direct answer. To put it plainly: single sign on and directory sync hotel case has to hold for single sign on and directory sync hotel case. single-sign-on-and-directory-sync has to hold at the same time. The sections below describe the order single sign on and directory sync hotel case is settled in. A single sign on and directory sync hotel case shows what each component must assume about the others. single sign on and directory sync hotel case is the interface that must be satisfied. Then commissioning starts on single sign on and directory sync hotel case.

  • Trace the interface — write down what hands over between lock, door and system at single sign on and directory sync hotel case
  • Verify the handover — record the sequence that proves single-sign-on-and-directory-sync works end to end
  • Preserve the trail — store the commissioning evidence with the file for two paths
  • Treat this as the single sign on and directory sync hotel case sequence, with single sign on and directory sync as the reference.

The evaluation week showed otherwise. Single sign on and directory sync are two mechanisms sharing one identity source, and they fail independently. Single sign on establishes the operator session in the back office; directory sync moves a person's entitlements to the doors. One is a login, the other a feed, and the first can work perfectly while the second leaves a leaver with access to a linen room.

These notes follow the order of that week: what each path carries, what each drops when its source cannot be reached, and who holds the fix when the two disagree.

The sentence in the brief that hid the real work

The brief asked for single sign on so staff would stop keeping several passwords. Underneath sat a requirement nobody wrote down: the same directory edit that changes a person's role has to change the doors that person opens, and that job fails differently. The reference set starts with Hotel Smart Lock System Integrator Guide.

Splitting the request into the people it covers unlocked the design.

SubjectSource of truthDoor side consumes
Back office operatorIdentity providerA signed session and its role
Hotel staff memberStaff directoryA person key, a status, a role code
GuestProperty systemA stay window and a room scope

A password problem, a joiner mover leaver problem and a guest stay problem sat inside one request. The single sign on and directory sync hotel case is manageable only once each row has its own owner, failure rule and test. The nearest catalogue entry is the SLK-002 Keypad RFID Lock for Guesthouses; the specific SKU is confirmed on its dated product page.

Two paths that leave the same directory

Everything below the identity provider is a different mechanism from everything beside it.

flowchart TD
    Directory[Staff directory] --> IdP[Identity provider]
    Directory --> Sync[Sync service]
    IdP --> Session[Operator session]
    Session --> Console[Access console]
    Sync --> Rules[Entitlement record]
    Rules --> Controller[Door controller]
    Controller --> Door[Reader and lock]
    Console --> Log[Audit record store]
    Controller --> Log

The upper branch ends in a session; the lower ends in a record a controller can evaluate at a door. The lock reports the state; the system decides what the state means, and where that decision sits depends on the configuration.

The branches fail in opposite directions. A person can be refused a console session while their door rights still work, which is what a termination that reached one path and not the other looks like.

Service accounts need their own line, because service account ownership for integrations is where quiet privilege grows. The sync service should sign in as an account of its own, never inheriting an employee lifecycle.

The reader to controller path is a third contract. The reader reports; the controller decides.

What the hotel staff directory integration has to carry

A hotel staff directory integration is only as good as its keys, so the first workshop question was which field identifies the same human on Monday and on Friday.

FieldWhat breaks when it is unstable
Person keyA leaver and a rehire become two people
Role codeRights never reach the intended doors
Status and datesAccess outlives the employment

An email address is a poor key because it changes and agencies reuse it; a display name is worse. Agree a mapping key before the first sync where no stable person key exists.

The role code is the second contract. A directory rarely knows which doors a supervisor opens, so that mapping lives in the access platform, where a renamed code becomes a silent access change unless unmapped codes raise a visible exception. Where one directory serves several properties, scope rules change with it, as set out in Single Sign on and Directory Sync for a Multifamily or Office Portfolio.

A promotion recorded at six in the morning

Directory edits happen at the wrong times. A promotion applied at six in the morning matters because the old badge is already walking the corridors.

Whatever the sync interval is, that badge keeps working until the controller receives the update. So the question is what the agreed interval is between a change recorded in the directory and the change taking effect at the door, written into the acceptance criteria rather than inherited as a platform default.

The staff joiner mover leaver workflow is the same mechanism carrying the opposite meaning, and that version carries the security weight. Ask what happens when the sync run fails on the evening a leaver is recorded, then ask what the evidence shows: the door event time and the directory edit time are two different numbers, and a report has to carry both.

The hour the directory could not be reached

A directory outage is a designed state, not a surprise. The directory outage degraded mode has to answer four questions.

QuestionWhat it decides
Do cached entitlements continueWhether doors work through the outage
What happens to queued changesWhether a Friday leaver is granted on Monday
Does the operator session surviveWhether the console is reachable at all
Who authorises the manual routeWhether the fallback is accountable

Ordering is the subtle one. Replay a queue in arrival order after an outage and a late change can land after the change that superseded it, re-granting a door the person had already lost. Correct handling applies changes by effective date and keeps the original edit time.

If the identity provider federates from the same directory, losing the directory takes the console session down too, and recovery becomes a named local administrator account with an owner, a reason field and a log the hotel reads.

CONFIRM-WITH-LOCAL-EGRESS: Confirm with the local authority having jurisdiction and the property safety reviewers that a directory outage cannot alter the approved escape arrangement or the power-loss behaviour of an affected door.

The outage belongs in the design, not in the manual.

When the desk still has to badge somebody

A property with guests in it does not wait for a directory. An agency worker arrives at seven, and the desk has a badge to issue whether or not the feed is running.

The manual route needs four written elements: who may authorise it, which doors it covers, when it expires, and what reconciles it. The last is the one hotels miss, because an unreconciled manual grant is an entitlement nobody owns and a badge nobody has withdrawn. It also has to carry its authoriser and its reason, otherwise a later audit cannot separate a deliberate exception from a fault.

Guests never appear in the directory

Guest access comes from the property system, not the staff directory, and the two must not be merged in a way that lets one person appear as both. Guest credential source separation is not tidiness; it answers a real question.

The fields collide naturally. Surnames repeat, staff may stay on site, and a guest and a housekeeper can share a family name in one building. Every entitlement record should carry the source system and the source identifier behind it, so a question about a door opening is answered by following one origin rather than by matching names.

The privacy position differs too. Staff records sit under an employment purpose, while a guest stay sits under a different purpose with its own retention and notice rules. The operator sign in for property systems belongs to the staff side only.

CONFIRM-WITH-LOCAL-PRIVACY: Have local counsel confirm with the property operator which identity fields may reach the access platform for staff and for guests, the retention periods for each, and who may search them.

Which clock answers which question

Three parties stamp events, and they do not stamp them at the same instant. The reconciliation question comes first: for a disputed door opening, which time do you believe. Clock ownership for access events is a design decision, not an inherited setting.

TimestampOwnerQuestion it answers
Directory edit timeStaff directoryWhen the change was recorded
Sync applied timeSync serviceWhen the door entitlement was written
Decision timeControllerWhen the door decided
Event timeLock or readerWhen the credential was presented
Receipt timePlatformWhen the platform received it

The audit log and the event memory on a device are not the same thing. Event memory is the buffer a controller holds when it cannot reach the platform, and it holds recent activity only; the audit log is the retained history. Ask where an event goes when the channel is interrupted, and what a reader sees when source time and receipt time differ.

Reading the logs after the fact

Most escalations arrive at the integrator as a symptom rather than a fault report.

SymptomUsual causeCheck firstWho acts
Removed employee still opens doorsSync failed, termination unmappedLast successful runAccess platform owner
Employee refused at the consoleGroup mapping in the identity providerSession logHotel IT
Joiner signs in, badge opens nothingRole code absent from the mappingException queueIntegrator
Door opens on rights the directory never showedManual or break glass issuanceManual issue logFront office manager
Sync reports success, doors unchangedCommand accepted but not appliedAcknowledgement trailAccess control engineer

The last row separates an integration from a demonstration. A platform that accepts a change and reports success has proved it received the instruction, not that a door changed. The party boundary in each row is argued in Who Owns Single Sign on and Directory Sync: Supplier, Integrator or Client.

It is worth pairing this with the smart lock commissioning checklist. That is the same question single sign on and directory sync hotel case has to answer here.

What to ask for before the design freeze

The requirement set for this work belongs in a document the hotel can sign, and Single Sign on and Directory Sync Requirements Document Template carries the list. Four items carry most of the weight: a federation description naming the identity provider and the applications in scope, the sync contract with its trigger, interval, ordering and reconciliation rules, the role code dictionary with its door set mapping, and a dated statement per SKU for the door hardware and controller.

The same question is worked through in more detail in smart lock testing after installation. That is the same question single sign on and directory sync hotel case has to answer here.Single Sign on and Directory Sync: The Test Plan a Buyer Should Demand turns the acceptance set into staged gates, and Single Sign on and Directory Sync Failure Patterns and How to Recover catalogues the failures that appear only in production.

Closing the notebook

Two findings survived the week. Single sign on and directory sync answer different questions and need different tests, because one ends in a session and the other ends in a record a door can act on. And the failures that matter at a hotel are the failures of identity key stability, of change ordering after an outage, and of the manual issuance nobody reconciles. When the mapping, the clock and the ordering rules are written down, the commercial conversation belongs at Request a Quote. The handover of those decisions is treated in Documenting Single Sign on and Directory Sync for Handover and Audit.

Winkelwagen
Uw ervaring op deze site wordt verbeterd door cookies toe te staan Cookiebeleid
Chat on WhatsApp