VistrUser guide

User guide

Monitor gates and occupancy

Monitor gate events, assist visitors, and verify presence records.

Your organization settings and account permissions determine which options are available.

All screens use fictional data. QR images and setup codes are examples and cannot be used to register.

Before you start

Sign in as Security or staff assigned to the location. Confirm the displayed location matches your post.

How the task works

Follow the main steps in order. Where a choice is shown, follow the branch that matches your situation.

  1. SecurityChoose the guard post
  2. SecurityReview events and the related identity
    • Visit foundOpen the detail panel and continue the same visit
    • Registration queue neededOpen Reception through the quick action
  3. SecurityOpen the gate with a reason when permitted
  4. System and staffCheck each device result
    • Response lost or uncertainCheck status; do not resend automatically
  5. SecurityConfirm conditions on site
Each label names who acts. Branches explain what changes when the condition applies.
Enlarge flow diagram

Steps

  1. Open Guard post and select your assigned location. Review events and gate status. Use quick actions to show the place QR, scan a guest QR, or open Reception. Available guest details can be reviewed directly in the Guard post panel.

    Guard post opens within the Security account’s assignment.Enlarge image
    Figure 1. Guard post opens within the Security account’s assignment.
    1. Guard post opens within the Security account’s assignment.

    Sample data · Security · 2026-10-13 · 2880 × 2000 px

    On a phone, select the assigned location and use the quick action needed for the task.Enlarge image
    Figure 2. On a phone, select the assigned location and use the quick action needed for the task.
    1. Check the event result before taking a service action.

    Sample data · Security · 2026-10-13 · 780 × 1688 px

    On a tablet, review gate events while keeping visitor service actions available.Enlarge image
    Figure 3. On a tablet, review gate events while keeping visitor service actions available.
    1. Check the event result before taking a service action.

    Sample data · Security · 2026-10-13 · 1640 × 2360 px

  2. Open Events, then Denied access photos to review captured images. Filters separate Not recognized, Access denied, and Check failed. Profile photos are separate. If the device did not send a photo, the card says so. Open details for the time, place, and device; select the photo to enlarge it.

    Read the inside list as a system record.Enlarge image
    Figure 4. Read the inside list as a system record.
    1. Read the inside list as a system record.

    Sample data · Security · 2026-10-13 · 2880 × 2000 px

  3. The list updates automatically while connected. Events held at the Edge arrive after recovery with their original times. One person may have several events. Notifications do not grant access or assign identity. Admins set retention under Settings, Gate event photos; the default is 90 days.

  4. When opening a gate, enter a reason and check each device result. Request sent does not mean the device confirmed it. Check status only reads results; do not resend just because a response was lost. Up to 20 recent requests from the last 24 hours can be reopened.

  5. In Who is inside, review the time, sources, groups, and estimate information. Delayed device records can make the data incomplete. A device confirmation is not proof that a person passed through the gate.

What to enter and why

Requirements depend on the destination and registration method.
FieldWhen neededPurposeExample
LocationWithin your assignmentLimits visible visits and events.Main lobby
Who is insideOperational informationBased on arrival/exit records; compare with the real situation.Occupancy list

Expected result

Staff have current records to support reception. Digital lists and roll call do not replace direct observation in an emergency.

If something goes wrong

Inside count differs from reality

Review entry/exit events and confirm on site. Report discrepancies to authorised staff. Individual occupancy corrections are not available in this phase.

Roll call

An Admin or Operator starts and closes the session. Security, Frontdesk, Admin, and Operator can mark people safe; Viewers read the results. The starting list remains a record. The initial view prioritises people not yet confirmed; turn off the filter to see everyone. A group mark counts every member. Printing includes the full list even when the screen is filtered. Leaving the screen does not close the session, and marking safe does not check a guest out.

Incomplete records

If the starting records are incomplete, zero remaining does not confirm that everyone is safe. Check conditions on site and follow organization procedures. Individual occupancy corrections and adding people outside the starting list are not available in this phase.

Blocklist and existing access

An Admin or Operator manages blocklist matches by name or phone. The same name may belong to different people. Adding or lifting a block does not automatically change active credentials. Check the identity, then use the permitted actions in Credentials. Changing a person’s status is an Admin action. Ending a visit also records checkout, so it differs from revoking access.

Related guides

← All guides

Image preview

Original screenshot