Identity Lifecycle Management
Every joiner, mover, and leaver event automaticallymapped to a physical access record.
When someone joins, changes roles, or leaves, systems are automatically updated. Door access usually doesn’t. It still depends on tickets and manual updates between HR, identity, and access systems.
SwiftConnect handles joiner, mover, leaver (JML) events — creating, modifying, and terminating records — by mapping identity attributes from sources such as Saviynt, SailPoint, Okta, Microsoft, Workday, or ServiceNow to your physical access system. It updates door, floor, and area access based on each person’s role.
The Foundation for Physical Access
- Identity lifecycle management is foundational. Without accurate user records, you cannot accurately and effectively assign permissions, revoke access, or audit compliance.
- When lifecycle operates automatically, physical access aligns with digital identity infrastructure using the same governance and real-time updates that manage application access.
- SwiftConnect works with the identity systems you already run as the source of truth — no rip-and-replace, no proprietary lock-in.
When someone leaves, their access leaves too. Every change flows from
the one source you already trust and reaches every system at once.
Reasons to Choose SwiftConnect
How it Works
Identity as Source of Truth
Whatever system already manages identity in your business serves as the authoritative source for the access control record that SwiftConnect maintains.
SwiftConnect connects to the systems you already run as the source of truth, Saviynt, SailPoint, Okta, Microsoft, Workday, or ServiceNow, and monitors them for changes. When a new employee is added to one of these systems, SwiftConnect automatically creates their record in each connected physical access control system where required, using attributes such as employee ID, email, name, role, department, location, and employment status.
Contractors who exist in your directory sync the same way. Contractors, vendors or visitors managed through separate systems or through ServiceNow, provision from that source instead. If no system is in place, SwiftConnect can serve as the identity store for physical access for non-employee identities. Each identity type flows from its appropriate source of truth.
Automated Lifecycle Events
User lifecycle changes trigger an immediate record update across every connected system.
When someone joins, SwiftConnect creates their record in every connected access control system with the correct attributes, and the record’s role-based access is used to grant day-one access. Role changes, location transfers, or department moves automatically update that record. Terminations or expiry dates deactivate the record and revoke access immediately.
The platform maintains synchronization continuously. If an employee’s name changes in Workday, the name on their access control record updates too. If a contractor’s permit expires in the upstream system, their record updates and access deactivates automatically.
One of Five Connected Use Cases
Identity Lifecycle Management is the first of five ways SwiftConnect automates physical access. Each stage feeds the next:
Identity Lifecycle Management
Create, update, and disable user records in physical access based on source(s)-of-truth.
Role-Based Access
Grant access to doors, floors, and zones by role and location.
Self-Service Access
Request extra access beyond a role, triggered by travel, projects, or AI assistants.
Access Recertification
Confirm people have only the access and credentials they need.
Audit
Retain decisions, changes, and critical events for compliance.
Automate Your Identity Lifecycle
SwiftConnect links existing identity systems to all physical access systems for automated joiner/mover/leaver records, eliminating manual provisioning. It is one of five use cases in the Connected Access Network: identity lifecycle, role-based access, self-service requests, recertification, and audit.