Skip to content

VisitorPass

Reception that runs without a receptionist.

Guests check themselves in from their own phones.

A credential opens the doors they are authorised for and leaves a record of who was on site and when. Nobody types anything on the guest's behalf, which is why a site with an unstaffed entrance works as well as a staffed one. There is nothing to install, for you or for them.

Request a demo

What it replaces

A paper logbook, a queue at the desk, and an identity check you pay for every visit.

Those are the three things every visit costs you today.

Before

  • A paper logbook at the door
  • Someone keying in details on the guest's behalf
  • An identity document handed across the desk
  • An identity check paid for on every single visit

After

  • A credential on the phone the guest already carries
  • Self check-in, so an unstaffed entrance works too
  • Verified once, reusable for every visit that follows
  • Access that stops working by itself when the visit ends

A visit, end to end

Booked in your calendar, completed on the guest's phone, closed on the way out.

01

Book the visit

From a calendar invitation, the dashboard, or the invitation API. The guest gets a personal email link and never creates an account.

02

Guest completes it on their phone

They work through whatever the visitor template requires, prove their identity if it asks for that, and receive the credential to their wallet.

03

Check in, get access, check out

The kiosk matches the credential to an active visit, your access control system provisions the template's access profile, and checkout closes the record.

An hour, or a season

The same flow for a 30-minute meeting and a six-month contract.

Short visits come in from the calendar: meetings, interviews, courses, deliveries. Long engagements are created from the dashboard or the API for temporary staff, contractors, maintenance, consultants, and auditors, where the window spans weeks or months rather than the length of a meeting. Visitor templates carry the difference.

Visitor templates

Each template sets what the guest completes before a credential is issued, whether identity verification is required, and which access profile the visit carries.

Calendar-triggered self-registration

Invite an external guest and copy a monitored mailbox: the visit registers itself, with no separate booking step for the host.

Access profiles, not door lists

The template decides which doors a visit authorises. Longer windows are where access control integration stops being optional.

Access ends when the visit does

Credentials are withdrawn at checkout or when the window closes, so there is nothing to collect at the desk.

Identity proofing when it matters

Optional by default and required per template. The longer the window, the more the binding to a verified person is worth.

Multi-location management

One console for every site. Standardise the policy across a region or a global footprint.

Works with what you already run

It slots between your systems and takes over none of them.

The credential follows the W3C Verifiable Credentials data model, SD-JWT, OpenID4VCI and OpenID4VP, so any conforming wallet can hold it, including an EU Digital Identity Wallet as those arrive. What runs your building stays yours.

Your doors

Your access control still decides

VisitorPass provisions the guest ahead of the visit and withdraws them after. Your system holds the authorisations and decides whether a door opens. It is not an access control system.

Your directory

Your directory stays the source of truth

Staff sign in through the identity provider you already run. Provisioning, deprovisioning and multi-factor authentication stay entirely with you, and VisitorPass never sees a password. It is not a replacement for your identity provider.

Your devices

There is nothing to install

No software on the check-in device, and nothing on the guest's phone beyond the wallet they already carry. The guest's phone never touches your network.

The reception console

One screen for the whole front desk.

Reception and admins run the day from a single dashboard: today's guests and contractors, who is on-site, who is running over, and which credentials are still pending, across every location you operate.

Preview of the VisitorPass reception console: today's visits with live status, the visitor and employee directories, and a credential audit log where every credential issued, accepted, presented, and revoked is anchored to a Partisia DID and independently verifiable.

Inside the console

Everything your team runs from one place.

Behind the guest's phone is a back office built for reception, hosts, and admins, with every visit, credential, and acknowledgement on a single, audit-ready surface.

Daily visits board

Every guest and contractor for the day on one screen: scheduled, on-site, overtime, and pending credentials at a glance.

A verifiable credential per visit

Each visit carries a credential anchored to Partisia's decentralised identity registry: issuer, wallet, and validity, not a name on a list.

Tamper-evident audit log

Every check-in and credential event is logged and marked "Verified by Partisia DID", audit-ready from the day you go live.

Visitor templates & safety acks

Configure intake fields and safety acknowledgements per visitor type; visitors mid-journey keep the version they were invited under.

Employee & visitor directory

Manage hosts, reception, and admins, and see a visitor's full cross-host history in one place.

Sign in with your own IdP

Staff sign in through your existing identity provider (Google Workspace, Entra ID, Okta) with no second password to manage.

In short

What a VisitorPass visit is made of.

8
Steps from booking to checkout, grouped into the three phases above.
6
Of those steps happen on the guest's own phone, not at your desk.
4
Open standards behind the credential: W3C VC, SD-JWT, OpenID4VCI, OpenID4VP.

Book a demo

See VisitorPass at your front door.

30 minutes is enough to see how VisitorPass moves your reception onto a credential without changing your access control stack. Tell us about your site and we'll be in touch within one business day.

  • Check-in from the guest's own phone, no clipboards
  • Template requirements completed before arrival
  • Optional identity proofing against MitID, AltID, or an EU wallet
  • Guidance for your specific use case

This Pipedrive form sets a cookie. Allow Forms cookies to load it, or see our privacy & cookie policy.