Skip to content
OpenAppPhysical access, simplified
Login

8. Test from the dashboard and portal

First, test as a registered user:

  1. Open the access-control screen for the demo portal.
  2. Trigger Open.
Access door screen with a lobby door photo and Open for the demo portal.(click to enlarge)
Access door screen with a lobby door photo and Open for the demo portal.
  1. Confirm the virtual door opens and Demo light turns on with it—portal Open runs the door and any configured entry lights together (unlike the per-entity buttons on the Virtual Demo Devices integration page).
  2. If auto-close for the door and auto-off for the light are still enabled on the portal device (the usual defaults, or the deploy fallbacks when a delay is unset), wait until the door returns to closed and the light to off without clicking Close or Turn off. You can change or disable those timers in portal configuration; see Auto-close semantics.

Then test as a visitor:

  1. Open a separate private/incognito browser window.
  2. Visit the public portal or invitation link.
Public portal directory as a visitor who is not signed in.(click to enlarge)
Public portal directory as a visitor who is not signed in.
  1. Confirm the virtual intercom loads and the allowed access action works. If you trigger Open as a visitor, expect the same door plus linked Demo light behavior as in steps 3–4 above (subject to the portal’s auto-close / auto-off settings).
Public portal guest view with a lobby door photo and Open after using an invitation link.(click to enlarge)
Public portal guest view with a lobby door photo and Open after using an invitation link.

You have exercised the same setup as an org member and as a visitor (portal or invitation). The door remains a normal entity in the API; the next step issues the smallest curl that runs switchable.open on that entity with your API key—not the multi-step access Open—without the dashboard.

← Demo access control · Open the door with the HTTP API →