University of Ottawa unifies physical and digital access with IGA

At a glance

What this is: The article describes how the University of Ottawa unified physical and digital access control through one IGA-led identity model, with RBAC and lifecycle processes extending across campus cards and IT access.

Why it matters: This matters because many IAM programmes still treat physical access, digital access, and lifecycle governance as separate workflows, even though role changes and approvals increasingly span all three.

Context

Physical access becomes an identity governance problem when campus cards, building entry, and digital entitlements are all managed through the same user record. The University of Ottawa case shows how identity data can be used to coordinate who gets in, what they can access, and how that access changes over time.

The governance gap is not the door or the badge on its own. It is the operational split between physical security systems and IAM processes, which creates duplicate approvals, slower onboarding, and inconsistent revocation when a person changes roles or leaves.

For higher education, the deeper point is lifecycle consistency. When role-based access control and user lifecycle management are applied across both physical and digital access, access decisions become more structured and auditable, rather than being rebuilt separately for each environment.

Key questions

Q: How should security teams govern physical and digital access through one identity model?

A: Start by mapping badges, facility rights, contractor credentials, and application entitlements to a single identity record. Then apply the same joiner-mover-leaver, certification, and revocation processes across both domains so access can be approved, reviewed, and removed consistently rather than through separate physical and digital evidence chains.

Q: Why does RBAC help when campus access spans buildings and IT systems?

A: RBAC reduces one-off access decisions by linking access to defined roles rather than individual doors or accounts. That matters when people move between jobs, because role changes can update both physical and digital permissions through the same governance logic, which lowers manual effort and improves auditability.

Q: What happens when physical access and digital access are managed separately?

A: Separate control planes usually produce policy gaps, slower provisioning, and inconsistent recovery when a badge or credential is lost. That separation can also weaken assurance because one team may approve a user for the building while another approves the same person for applications with different checks. A unified model reduces those handoff failures and keeps access decisions more consistent.

Q: How can teams tell whether access governance is actually working?

A: Look for short revocation times, low rates of stale entitlements, and repeatable access review outcomes across systems. If accounts remain active after role changes or offboarding, governance is not effective. Good measurement focuses on whether access is removed when it stops being justified.

Technical breakdown

How RBAC extends to physical access

Role-based access control assigns access based on a defined job or function rather than door-by-door or request-by-request handling. In this case, RBAC was used to map campus roles to physical access rights, which is unusual because physical security is often configured manually and inconsistently. The technical change is not just policy abstraction. It is a shared entitlement model where one role can drive both digital permissions and card-based access, reducing repeated approvals and making access rules easier to govern across systems.

Practical implication: treat physical access rights as governed entitlements, not as isolated security settings.

Why lifecycle management matters across badges and IT accounts

Lifecycle management covers the joiner, mover, and leaver process across identity types, including badge access and IT access. Here, that means a role change or employment change should update both the universal card system and the digital identity record through the same governance flow. The benefit is fewer stale permissions and less duplication, but the technical requirement is strong data consistency between identity records, card credentials, group memberships, and approval routing. Without that, the system fragments again even if the policy looks unified.

Practical implication: align card issuance, role changes, and offboarding to a single lifecycle workflow.

What the Genetec and IGA integration changes

The direct database integration between the physical security system and the IGA platform allows identity data to move between operational systems and governance controls. The internal API gateway adds another layer of orchestration, linking identity records to card credentials, group memberships, and photographs. That architecture matters because it turns access administration into a governed data flow rather than a manual reconciliation task. The main technical challenge shifts from user entry to data integrity, authorization routing, and avoiding duplicated identity sources of truth.

Practical implication: design the integration around authoritative identity data and controlled routing, not around ad hoc sync scripts.

NHI Mgmt Group analysis

Physical access is now an identity governance domain, not a facilities exception. The University of Ottawa case shows that badge issuance, building access, and digital entitlements can be governed through the same identity model when organisations are willing to treat physical access as lifecycle-managed entitlement. That collapses a long-standing split between facilities operations and IAM. The practical conclusion is that access governance programmes should stop assuming physical access sits outside identity architecture.

RBAC becomes more valuable when access spans both digital systems and physical spaces. In most organisations, physical access is handled as a bespoke control plane with manual exceptions and local ownership. Once roles drive both card access and IT permissions, RBAC becomes a shared governance language that reduces duplicated policy logic. The implication is that role design, not just badge administration, becomes the lever for consistency across the campus environment.

Lifecycle consistency is the real control surface here. The article’s strongest signal is not the integration itself, but the ability to keep role changes, approvals, and revocation aligned across systems. That aligns with NIST-CSF access governance expectations and with the broader NHI management principle that access must be governed at the point of issuance and change. Practitioners should see this as a governance architecture problem, not a facilities modernization project.

Identity data becomes the control plane once approval routing depends on it. The use of metadata to route entitlement requests to the right supervisor shows how governance logic can be embedded in identity records rather than handled outside them. That creates cleaner authorization paths, but it also raises the bar for data quality and process design. The lesson is that unified access only works when identity attributes are accurate enough to drive decisions without manual repair.

University access modernization reveals a broader higher-ed model. The University of Ottawa’s approach suggests that higher education can move from fragmented access administration to role-driven governance without rebuilding every workflow from scratch. The article points to reuse of existing rules, structured approvals, and federated data flows as the practical pattern. The implication for other institutions is clear: modernisation succeeds when access policy, lifecycle process, and system integration are designed as one programme.

What this signals

Unified access governance only works when identity data becomes authoritative across both physical and digital systems. Once a campus card, building permission, and IT account all depend on the same record, organisations have to manage entitlement changes as a lifecycle event rather than a local facilities task. That shifts the operational centre of gravity from door control to identity governance.

Role-based access control is the named concept this case surfaces for higher education. The practical value is not that RBAC is new, but that it can reduce duplicated access logic when a university wants one control plane for badges and systems. The implication for practitioners is that role design and attribute quality now matter as much in physical access as they do in application access.

For practitioners

• Unify physical and digital access governance Map badge access, building permissions, and IT entitlements into a single identity model so role changes propagate through one approval path rather than parallel processes.
• Apply RBAC to campus access decisions Define role sets for common university functions and use them to drive both physical and digital access assignments instead of handling each door or account separately.
• Connect lifecycle events to access revocation Tie joiner, mover, and leaver events to badge credentials, group memberships, and application access so offboarding and role changes are handled together.
• Route requests through authoritative metadata Use identity metadata to send entitlement approvals to the correct supervisor or owner, and keep the routing logic aligned to governance requirements.
• Reduce duplicate access workflows Review where the same identity data is being processed twice for physical and digital access, then collapse the redundant steps into one controlled workflow.

Key takeaways

• The core issue is not a badge system upgrade but the governance problem of keeping physical and digital access aligned through one identity lifecycle.
• The article shows that RBAC, lifecycle management, and direct system integration can reduce manual work while improving consistency across campus access controls.
• For practitioners, the lesson is to unify identity records and approval routing before trying to modernize access in separate physical and digital tracks.

Key terms

• Identity Lifecycle Governance: Identity lifecycle governance is the set of processes that create, change, review, rotate, and revoke access across human and non-human identities. It matters because access risk usually increases when lifecycle events are slow, incomplete, or disconnected from the systems that rely on them.
• Role-Based Access Control: A model that grants permissions by assigning identities to predefined roles. It works well when jobs are stable and access patterns are predictable, but it becomes brittle when exceptions pile up. In practice, role design must stay small enough to audit and broad enough to avoid endless custom variants.
• Entitlement Routing: Entitlement routing is the process of directing an access request to the correct approver or owner based on metadata, role, or context. It helps identity systems keep governance structured when access decisions need to move across multiple systems and approval chains.
• Converged Physical And Digital Access: Converged physical and digital access is an identity model that uses one credential strategy across building entry and digital systems such as cloud apps or VPNs. It reduces fragmentation, improves policy consistency, and gives security teams a single control plane for authentication, governance, and lifecycle management.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are building or maturing an IAM programme, it is worth exploring.