Yes. Modern access platforms support integration with HR systems, Active Directory, Azure AD, and identity providers via SCIM, LDAP or API. Manguard scopes the integration during the site survey, agrees the source of truth for joiner-mover-leaver events with your IT team, and configures the access platform so credentials are provisioned and revoked automatically when HR records change. This removes the manual gap that causes most lapsed-credential audit findings.

Multi-site estates are managed from a single centralised access platform with role-based administration. One credential can be authorised across multiple sites, access levels are defined per zone and per shift, and changes propagate to every controller in near real time. Site administrators get scoped permissions for their own location while head office security retains an estate-wide view, audit trail and reporting.

All three, and most sites combine them by zone. Proximity and smart cards remain the default for general access, mobile credentials (Bluetooth and NFC) suit corporate and contractor flows, and biometrics (fingerprint, facial, iris) are specified for high-security zones such as data centre cages, pharma cleanrooms and cash rooms. The credential mix is decided during the site survey against the threat model and user experience requirements, not by product preference.

Yes. Critical access events – door-forced-open, door-held-open, after-hours access, repeated invalid credential attempts, anti-passback and tailgating alarms – can route directly to operators in the EN 50518:2019 Category I Command and Control Centre. The same operators handle CCTV verification and keyholder dispatch, so an access alarm is investigated, verified on camera and escalated through one accountable chain rather than three.

Access logs, visitor records and biometric templates are personal data under GDPR. Manguard configures the system around documented retention periods, role-based access to logs, audit logging of administrator actions and secure deletion. Biometric data is treated as special category data with explicit consent flows and template-on-device options where the threat model allows it. We support clients on Data Protection Impact Assessments and subject access requests covering the access platform.

Yes. Service takeover is common when a multi-site client consolidates providers or an incumbent installer is not meeting SLA. We carry out a system audit covering the head end software, controllers, readers, credential database and network topology, document the current state, and either continue with the existing platform under a new service agreement or specify a migration path with a managed cutover. Credentials and access permissions are preserved through the transition.

If the access platform is integrated with HR or identity, revocation is automatic and propagates to every controller within minutes of the HR record changing. Without integration, revocation is manual and depends on the administrator workflow agreed in the service specification. We strongly recommend identity integration for any client with regular joiner-mover-leaver volume, because manual revocation is the source of most audit findings on lapsed access.

Yes. Mantraps, interlocked door pairs, anti-passback zones, two-person rule and airlock-style cleanroom access are routinely specified into pharma manufacturing, data centre cage and cash room environments. The configuration is designed during the site survey against the operational flow, gowning protocol or compliance requirement, and commissioned with the client’s operations team so the access logic matches actual working practice rather than just the drawing.