← Back to journal

Access / JAY CLOUD JOURNAL

Physical identity and access management (PIAM) guide

Physical identity and access management (PIAM) connects HR data to building access. Learn how to manage joiners, movers, leavers and audit evidence.

Poksundo Team ·

Physical identity and access management (PIAM) guide

Physical identity and access management (PIAM) connects a person’s identity and employment status to the physical spaces they may enter. HR is the natural source of truth for employee identity, while an HCM-driven workplace layer turns workforce changes into access policies and lifecycle actions. For mid-market and enterprise organizations, the goal is consistent joiner, mover and leaver processes without maintaining a separate employee record at every building.

What physical identity and access management (PIAM) means

PIAM is the discipline of managing physical identities, access permissions and their lifecycle across workplaces. It connects the business context of a person—such as employment status, department or assigned site—with the systems that control entry.

Traditional access control answers a narrower question: should this credential open this door? PIAM adds the organizational questions behind that decision: who owns the identity, why is access appropriate, what changed and when should access end?

A useful distinction is:

  • Identity: the person and the authoritative record describing them.
  • Entitlement: the physical access they should receive under organizational policy.
  • Credential: the means used to identify them at an access point.
  • Lifecycle: the events that create, change or remove access.

PIAM is not necessarily a single product category with identical functionality across vendors. Organizations can pursue PIAM outcomes through an HCM-connected layer, dedicated identity software or a combination of systems. Evaluate the operating model rather than relying on the label.

Why HR is the natural source of truth

HR already manages the events that matter most to employee access: hiring, transfers, changes in employment status and departure. Re-entering those events into a separate building-security database creates another record to maintain and another opportunity for inconsistency.

An HCM-led approach starts with a simple principle: employee identity should originate where the employment relationship is maintained. Facilities and security then define how that information affects physical access.

That does not mean HR should decide every door permission. HR owns workforce facts; security owns access policy; facilities understands the buildings; IT owns integration and technical controls. Keeping those responsibilities distinct makes automation easier to govern.

Authoritative does not mean flawless

An HR record may contain an outdated location, an incomplete department assignment or a departure date entered late. Connecting that record to building access makes data quality operationally important.

Before automating access decisions, agree which fields are authoritative, who maintains them and how exceptions are handled. Also distinguish employees from contractors and visitors: not every person entering a workplace necessarily has an HCM record. Define an accountable owner and an appropriate lifecycle for each population rather than forcing everyone into the employee model.

Turn joiner, mover and leaver events into access rules

The strongest PIAM business case is often lifecycle consistency. A new starter should receive appropriate access, an internal transfer should trigger a review of existing permissions, and a departure should not depend on someone remembering a separate badge task.

Lifecycle event Authoritative input to define Physical access outcome to design Evidence to request
Joiner Employment status, start date, site and role Appropriate access becomes available at the agreed time Identity creation and permission history
Mover Department, role or location change New access is assigned and obsolete access is addressed Before-and-after permissions and change history
Leaver Departure or status change Access is removed according to policy Revocation event and any exception record
Temporary assignment Approved scope and duration Additional access has a defined owner and end condition Approval, assignment and removal evidence

This table is a design checklist, not a claim that every platform implements each outcome identically. Ask vendors to demonstrate the timing, mapping and evidence available for your actual processes.

The mover process deserves particular attention. Adding access to a new department without addressing previous permissions can leave an employee with more access than their current role requires. Test changes in both directions, not just initial provisioning.

For a closer look at departure workflows, see the guide to employee offboarding and physical access revocation.

How an HCM-driven layer delivers PIAM outcomes

An HCM-driven architecture connects workforce data to the physical workplace without asking the access system to become another HR database. The HCM system continues to manage workforce records; the connected layer derives workplace rules from that data and links them to access infrastructure.

jay cloud by Poksundo is a connected layer for Time, Access, Visitor and Life Safety, driven by HCM data. It has five native HCM connections: SAP, Workday, HiBob, Hubdrive and Access People.

Its described workflow has three parts:

  1. Connect the HCM system and synchronize workforce data.
  2. Derive access rights, shift models and visitor policies from HR data, with existing hardware coming along.
  3. Let hires, moves and departures inform the workplace without separate tickets.

jay cloud is 100% cloud, with no on-premise infrastructure, and states that departures require zero manual updates. It also provides central device management with automatic updates and security patches, and states that all hardware for time and access can be integrated.

These are relevant building blocks for PIAM. The procurement task is to validate their application to your organization: which HR fields drive which rules, how effective dates are handled and what happens when a record is incomplete. Have the team validate your specific hardware estate rather than treating a general integration statement as a completed deployment design.

Match the integration to your HCM environment

For SAP organizations, jay cloud was developed in close cooperation with SAP through the Co-Innovation Program and is native on SAP Business Technology Platform. It has a SAP-certified interface for SuccessFactors Time Tracking Service and Time Sheet; that certification should not be generalized into a broader certification claim for every access workflow.

The SAP partner listing provides supporting product information. Related planning guidance is available in SAP SuccessFactors time clock integration and Workday time clock and access integration.

Separate physical access policy from administrative permissions

“Role-based access” can describe two different controls. One governs what an employee may enter; the other governs what an administrator may view or change inside the management platform.

For physical access, define policy using business-relevant attributes and exceptions. A site assignment might inform a standard access profile, while a restricted area may need a separate approval. These are policy examples to evaluate, not assumptions about a particular product’s configuration options.

For administrative access, apply the same discipline to platform users. HR, security and facilities may need different responsibilities. Ask who can change rules, inspect records and administer devices.

jay cloud lists role-based access controls, end-to-end encryption and full audit trails among its security capabilities. During evaluation, request a demonstration of the administrative roles and audit records relevant to your governance model. Do not assume that a security feature name answers every segregation-of-duties requirement.

Make audit trails useful, not merely available

An audit trail should help explain a decision or reconstruct an event. A long list of door events alone may not explain why a person had access in the first place.

Build your assessment around practical questions:

  • Which workforce change initiated an access change?
  • What policy or administrative action determined the outcome?
  • When did the change occur, and which records support it?
  • Can authorized reviewers retrieve the evidence they need?

Request representative records for a new hire, transfer, departure and manual exception. Review whether the evidence answers your internal audit questions, and establish retention and access rules for those records.

Employee data and access histories can raise privacy and regulatory considerations. Confirm applicable obligations, retention requirements and lawful processing arrangements with counsel. Software capabilities are not a substitute for that assessment.

Connect identity governance to emergency accountability

The identity model also matters during an evacuation. Employees, visitors and contractors may appear in different systems, making it harder to establish who could be on site and who has been accounted for.

jay cloud’s Life Safety capabilities include real-time attendance status, intelligent muster points and audit-ready visibility. Its emergency roll call combines time, access, visitor and HR records.

These inputs serve different purposes. A time record, door event or visitor record should not automatically be treated as definitive proof of someone’s current location. Emergency procedures still need reconciliation, assigned responsibilities and drills that test realistic exceptions.

Use the emergency headcount guide to examine evacuation accountability alongside the technology. Confirm applicable emergency-planning obligations with counsel and the responsible safety professionals.

Choose a rollout scope that exposes real complexity

For a mid-market organization, the priority may be reducing duplicate employee administration across a few sites. For an enterprise, the harder questions may involve different HR processes, multiple hardware estates and local policy variations.

Start with one representative location and a defined employee population. Map the authoritative fields, standard access rules, exception owners and departure process before expanding.

A useful pilot includes more than a successful new hire. Test a transfer, a corrected HR record, a departure and a situation where information is unavailable. Ask how discrepancies are detected and resolved rather than assuming every event will arrive perfectly.

Agree success criteria before the pilot: fewer separate identity-maintenance steps, reliable lifecycle outcomes and usable audit evidence. Those are evaluation goals, not guaranteed product results. Expansion should follow demonstrated processes that HR, IT, facilities and security can all support.

Frequently asked questions

Is PIAM the same as physical access control?

No. Physical access control governs entry at doors and other access points, while PIAM connects those permissions to identity, organizational policy and lifecycle changes. The two are complementary: PIAM provides the identity context behind access decisions.

Should HR own physical access permissions?

HR should generally own authoritative employee data, not every access decision. Security and facilities should define physical access policies, with IT responsible for integration and technical governance. Clear ownership makes HCM-driven automation more accountable.

Can PIAM support contractors and visitors?

A PIAM program can include employees, contractors and visitors, but each population needs an authoritative record and accountable owner. Do not assume everyone exists in the HCM system. Ask vendors how their current capabilities handle nonemployee identities and lifecycle rules.

Does jay cloud require replacing existing access hardware?

jay cloud states that existing hardware comes along and that all hardware for time and access can be integrated. It also provides central device management with automatic updates and security patches. Validate your specific readers, doors and terminals during technical discovery.

Does an audit trail make an organization compliant?

No. Audit trails provide evidence, but compliance also depends on policies, operating practices and applicable obligations. Confirm requirements with counsel and test whether the available records support your audit and retention needs.

Make workforce identity the starting point

Physical identity and access management (PIAM) works best when workforce facts, access policy and lifecycle responsibilities are clearly connected. Start with the joiner, mover and leaver processes, then validate the integration, hardware and evidence against your real operating environment.

Talk to the jay cloud team about connecting your HCM data to Time, Access, Visitor and Life Safety.

More from the journal