Cloud access control

One tap at the door. Access granted, hours recorded.

TeamzPass issues credentials to whatever your team already carries - phone, wallet pass, badge, fingerprint - and turns every door event into an access decision and a timesheet entry at the same moment.

Start 14-day trial See how it works

No card details. Works with the readers you already own.

North entrance Zone 02 · Head office
Wallet Elena Rosen Operations · Shift 07:00–15:00 Apple Wallet · CRD-4471
Live event log
  • 08:59:12 North entrance · Elena Rosen granted clock-in recorded
  • 08:57:40 North entrance · Daniel Weiss granted clock-in recorded
  • 08:56:03 Server room · Daniel Weiss denied outside schedule
  • 08:54:55 Lobby · Visitor pass VIS-118 granted host notified

Why TeamzPass

The door already knows who arrived. Most systems throw that away.

An access controller decides yes or no and forgets. A time clock asks people to say what the door just saw. TeamzPass keeps both sides of the same event, so the badge that opens a door is also the record of the shift that started.

Access control on its own

  • Knows who opened which door, and nothing else
  • Payroll waits on a separate clock-in
  • Two directories to keep in step
  • Leavers stay in one system after they are removed from the other

TeamzPass

  • One event becomes an access decision and an attendance record
  • Timesheets fill themselves as people arrive
  • One directory, one set of permissions
  • Revoking someone closes the door and stops the clock

Credentials

Whatever your team already carries

Pick per person or per site. Change your mind later without touching the reader on the wall.

  • Apple Wallet & Google Wallet

    A pass on the phone people already unlock forty times a day. Issued remotely, before the first shift.

  • Phone NFC & Bluetooth

    Tap or approach. Works with the phone locked and with gloves on.

  • Fingerprint & face

    For doors where the credential must not be lendable. Templates stay on the reader.

  • Card, fob & keypad

    Keep the plastic you have. MIFARE, DESFire and PIN entry all report to the same log.

  • Visitor QR pass

    A time-limited link for guests and contractors, scoped to specific doors and hours.

Credential lifecycle

Issue, tap, revoke

Three moments. All three happen from the same screen, wherever you are.

  1. 1

    Issue

    Add someone once - name, site, zones, hours. Their credential arrives on their phone before their first day, with nothing to hand over in person.

  2. 2

    Tap

    The reader decides in under a second and logs the event. If the line is down it keeps deciding from its own cached rules, then syncs when the connection returns.

  3. 3

    Revoke

    One click removes the credential everywhere, ends the schedule and closes the timesheet. No badge to chase down after a resignation.

What you get

Everything your building needs. Nothing it doesn’t.

Eight features. One platform. One contract.

Explore all features

  • Zones & schedules

    Group doors into zones, then say who may pass and when. Rules by person, role, department or site.

  • Offline resilience

    Controllers cache their rules. A dropped connection never means a locked-out morning shift.

  • Attendance from the door

    The first tap starts the shift, the last one ends it. Overtime, breaks and absences follow from real events.

  • Audit trail

    Every grant, denial and rule change kept with a timestamp and an actor. Exportable for an auditor or an incident.

  • Who is in the building

    A live roll-call for a fire drill or an evacuation, guests included.

  • Directory & single sign-on

    Azure AD, Google Workspace, Okta and SAML 2.0. People arrive and leave through the systems you already run.

  • Multi-site

    One tenant, many buildings, local rules per building and a single view across all of them.

  • Payroll exports

    Hours leave as the file your payroll provider expects, not as a screenshot of a table.

Built to hold up

Reliability the building can lean on

Access control fails the moment it cannot be trusted. TeamzPass is built so the door keeps deciding on its own, the record stays complete, and a busy morning never depends on a good connection.

Offline-first
controllers keep deciding without a live connection
Sub-second
access decisions at every reader
Full log
every grant, denial and rule change kept with a timestamp
One event
a door tap becomes an access decision and a timesheet entry

Questions

Asked before every rollout

Do we have to replace the readers we already have?
Usually not. TeamzPass talks to standard controllers and to MIFARE and DESFire readers, so most sites keep the hardware on the wall and change what decides in the cloud behind it. We check your model list before you buy anything.
What happens to the doors if the internet goes down?
Controllers hold their current rules locally and keep granting and denying access on their own. Events queue up and sync as soon as the connection is back, so the log stays complete and nobody is stuck outside.
Can a phone credential be shared with someone else?
A wallet pass is bound to the device it was issued to and can be revoked in one click. For doors where lending must be impossible - a cash room, a lab, a pharmacy store - use fingerprint or face at that door and keep phones for everything else.
Does the attendance side work if we already have payroll software?
Yes. TeamzPass produces the hours; your payroll software keeps paying them. Exports are built for the common providers, and there is a REST API when a file is not enough.
How long does a rollout take?
A single site with existing readers is usually live within a week: connect the controllers, import people from your directory, set zones and hours, issue credentials. Multi-site rollouts run building by building on the same tenant.

Open the first door this week

Start a 14-day trial with your own doors and people, or walk through it with our team first.

Start 14-day trial Book a walkthrough