Skip to content

Visitor Provisioning

Every visitor registered in VisitorPass gets a carrier in AEOS once their credential is issued and they have a visit today or tomorrow: a visitor under their name, valid for their run of visit days, holding their badge and the authorisation templates the visit grants. VisitorPass sends the carrier over the channel the integration keeps open, so nothing is configured in the service beyond the installation.

AEOS checks only the carrier's dates, not its times: the visitor can open the doors their templates grant all day on each of those dates, whatever time their visits start and end.

Prepare AEOS

  1. Add these functions to the VisitorPass integration role:

    Function (English UI) Danish UI
    Person, Visitor, Search Person, Gæst, Søg
    Person, Visitor, Announce Person, Gæst, Opret
    Person, Visitor, Issue identifier Person, Gæst, Udsted ID-nøgle

  2. On the AEOS page in VisitorPass, under Visitor Provisioning, tick Give visitors an AEOS carrier, choose the AEOS time zone the AEOS server dates visits in, and click Save.

  3. Under AEOS templates, click Refresh from AEOS, and Manage each authorisation template visitors are to be given.

Never turn Visitor Provisioning on for an organisation that uses Credential Issued.

VisitorPass manages those templates on visitor carriers, and leaves every other template alone.

Verify

  1. Register a visit today in VisitorPass for a test visitor, and take the credential into a wallet.

  2. Check that the integration gave the visitor a badge in AEOS:

    Select-String -Path logs\out.log -Pattern 'Assigned badge' | Select-Object -Last 5

  3. Find the visitor in the AEOS web client, and check its validity dates and authorisation templates. The arrival time shown there is recorded, but only the dates limit access.

What's Next