The current Openpath Jira and Confluence instances will be migrated to the MSI On-Premise solution from August 9th-11th, the current platform will be set to read-only and all future usage will be in the Avigilon Instance. Please ensure access to MSI Jira & MSI Confluence, both are accessible through OKTA. For additional information and details please refer to the Atlassian migration page

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

The Last to Leave feature in the Avigilon Alta Open mobile app works by setting the entry back to its default entry state. For Last to Leave to work, the entry must have an Entry Schedule assigned to it and the Schedule must have “Trigger after an unlock included in” enabled.

To enable Last to Leave:

  1. Go to https://control.openpath.com/login and log in. To access the European Control Center, please go to https://control.eu.openpath.com/login.

  2. Go to Sites > Entry Schedules and click the plus (+) sign in the top right corner to Create a Schedule.

  3. Create an Entry Schedule according to your hours of operation and assign it to appropriate entries; see How do I assign Schedules to Entries?

  4. When creating the Entry Schedule, ensure that you enable Trigger after an unlock method included in and select the appropriate Entry State.

    1. In this example, the Scheduled State is Unlocked, which won’t take effect until someone unlocks using a method included in Convenience (any unlock method); for an alternate setup, read How do I configure Executive First-In?

Once saved and applied to your entries, a user will be able to tap Last to Leave in the Avigilon Alta Open mobile app and revert the Entry’s scheduled state (in this example, Unlocked) to its default state (Convenience).

  • No labels