Features
From the pass in the wallet to the lock on the door
The parts below are one product, not modules you assemble: the pass on the phone, the reader on the wall, and the platform that decides who gets in.
Wallet passes
The badge people carry on the phone they already own.
Apple Wallet and Google Wallet
Employee badges and access passes in the wallet app on the phone, issued remotely before the first day.
Express Mode
With Express Mode, you don’t need to wake your iPhone or Apple Watch or open any apps to use your employee badge in Apple Wallet. Just tap your device on the reader to unlock.
Updated over the air
Change a name, a photo or a site and the pass updates itself on the phone.
Bound to one phone
A pass cannot be lent like a card, and it is removed in one click.
Works with your access system
Wallet credentials for the access control system you already run.
Issue in teamzPass or by API
Create and revoke credentials in the teamzPass platform, or from your own software through the teamzPass API.
A code for every credential
Each credential has its own code. Copy it into your existing access control system, much like adding a card number.
Your readers, configured
Readers that already support wallet passes are configured to read teamzPass credentials, a very secure method. Readers that do not are replaced with wallet-ready readers from teamzPass.
Doors stay in your system
You keep managing doors, zones and schedules where you manage them today. teamzPass looks after the credentials.
Credential management
Every pass, card and PIN, from one screen.
Issue and revoke remotely
Send a badge to a new starter in another city, or remove it from a leaver, without anyone visiting reception.
Several credentials per person
A wallet pass for most doors, a card or a fingerprint where a site needs one, all on the same record.
Bulk issue from your directory
Import a site’s people and send every pass in one go.
Directory sync and SSO
Azure AD, Google Workspace, Okta, SAML 2.0. Joiners and leavers flow in from HR.
Readers and controllers
What happens in the second between a credential and a lock.
Wallet-ready readers
Readers that accept Apple Wallet and Google Wallet passes, for doors whose current readers do not support them.
Sub-second decisions
Grant or deny before someone reaches for the handle, from cached rules on the controller.
Offline controllers
Controllers hold their rules locally, so a dropped connection never locks anyone out.
One log for every reader type
Wallet, MIFARE, DESFire, BLE, biometric and keypad readers report to one log in one format.
Cloud access control
Who may pass, where, and when.
Zones
Group doors the way the building actually works: floors, wings, plant rooms, gates.
Schedules
Access by time of day and day of week. Holidays and site closures included.
Roles and departments
Assign rules to a role once; everyone who joins it inherits them.
Anti-passback and alerts
Stop one credential walking two people through, and get an alert when a door is held open or a duress PIN is used.
Visitors and evidence
Guests, contractors, and the record afterwards.
Time-limited invitations
Send a pass or a code that only works on the right doors on the right afternoon.
Host notification and roll-call
The host knows the moment a visitor arrives, and one live roll-call covers staff and guests.
Audit trail
Grants, denials, rule changes and credential issues, each with a timestamp and an actor.
Attendance, if you want it
Optional: door events can also feed attendance reports, payroll exports and the REST API.
See it on your own doors
A call with our team about your sites, your people and your readers.