You can push Security Center cardholders to a DMP intrusion panel, where they become user codes.
Before you begin
What you should know
- Push to panel
- Exports all Security Center cardholders to the panel and converts them to user codes. Updates, adds, and deletes user codes to match the cardholders in Security Center.
- Force push to panel
- Deletes all users from the intrusion panel, and then exports all Security Center cardholders listed to the panel.
- Cardholders must be assigned at least one profile to have access to the panel. Cardholders without profiles don't have privileges on the panel.
- The DMP 150 series panels have up to four profiles per user.
- The DMP 100 series panels have one profile per user.
- If a cardholder is in different groups, the profiles are merged. For example: Group A has profiles 3 and 4. Bob has profile 1 and 2, and is assigned to Group A. Bob will be pushed to the panel with profiles 1, 2, 3, and 4.
- If a cardholder has more profiles than is supported by the panel, only the first profiles are kept, all extra profiles are ignored. For example: Group A has profiles 3 and 4, Group B has profiles 5, 6, 7, 8. Bob has profile 1 and 2, and is assigned to Group A and Group B. Bob will be pushed to the panel with profiles 1, 2, 3, and 4, and the profiles 5, 6, 7, 8 are ignored.
- When you export cardholder lists from Security Center to a DMP intrusion panel, you can use an exclusion list to keep certain cardholders from being pushed to the panel, or to remove them during the next synchronization. For example, you can create an exclusion group for employees who are on vacation, and deny access to those employees' credentials while they are away.
- Setting a cardholder's card credential to Stolen in Security Center causes that credential to be deleted from the DMP intrusion panel during synchronization.
- Inactive users pushed to XR150-series panels are deleted.