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.

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. Decide which AEOS authorisation templates visitors are to be given, and send Partisia their ids from step 8 of the installation.

   Partisia staff

   PRODUCTION.md in the visitorpass-aeos-integration repository › Visitor Provisioning

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 and authorisation templates.

What's Next

• Door Opening: opening doors with the visitor's badge.