Overview
Operator Challenge displays information to an operator about a card access request and optionally requires the operator to manually grant or deny access. This feature is commonly used for:
- Visual verification of users at secure doors (with CCTV and user photos).
- Random bag searches or drug tests via the random selection feature.
- Manual access granting for users who would otherwise be denied.
The Challenge dialog is fully customisable — you can add CCTV streams, user photos, Allow/Deny buttons, custom text with HTML formatting, challenge history, and embedded web pages. Task Actions can be triggered automatically on challenge events.
Document version: Based on Controller firmware V3.0.2 and Integriti software V3.1.0.6951. Later versions may have additional features.
Prerequisites
- Integriti System Designer with installer-level access.
- Controller firmware V3.0.2 or later.
- Integriti communications tasks configured.
- Reader modules on the controller with the Ask PC option enabled.
- Users configured with the Ask PC option (for users who should trigger challenges).
- CCTV cameras configured in the system (if using CCTV in the challenge layout).
Step-by-Step
Configure Hardware for Operator Challenge
- In Integriti System Designer, click the Controllers tab and select the controller.
- Double-click a reader module that will be used for Operator Challenge.
- Expand Readers → Reader n (where n is the reader number).
- Tick the Ask PC option.
- Save and close the editor window.
- Repeat steps 2–5 for any additional reader modules.
Configure Users for Operator Challenge
For a single user:
- Click the Users tab.
- Double-click a user that should trigger Operator Challenge.
- Expand User Options.
- Tick the Ask PC option.
- Save and close.
For multiple users:
- Select a group of users.
- Right-click one of the selected users and choose Edit.
- Expand User Options.
- Tick the Ask PC option.
- Save and close — this applies to all selected users.
Create a Challenge Definition
- In Integriti System Designer, click the Operator Challenge tab.
- Click Add New and give the definition a name.
Configure “What To Challenge” — Doors
- Click the Doors tab.
- Add doors by one of these methods:
- Individual doors: Click the Add button on the Doors tab.
- By site/keyword: Click the Sites/Keywords tab and add sites.
- By filter: Create a filter rule.
Must specify at least one Door, Site/Keyword, or Filter.
Configure “What To Challenge” — Users
- Click the Users tab.
- Add users by the same methods as doors (individual, site/keyword, or filter).
Must specify at least one User, Site/Keyword, or Filter.
Configure Challenge Behaviour
- Click the Challenge Settings tab.
- Show Challenge To Operator:
- Never: Challenge never displays; controller processes user based on permissions after 20-second timeout.
- Always: Challenge appears on every access event.
- Only on Random Selection: Challenge appears randomly based on X occurrences out of Y challenges (e.g. 1/3 = 33% chance).
- Requires Operator Input: Same options as above. When not required, the controller processes based on permissions.
- Set X Occurrences and Out of Y Challenges for the random percentage.
- Optionally enter a Random Selection Message to display to the operator.
Design the Challenge Response Layout
- Click the Response Layout tab. The layout is configured like an Alert Response Plan. Available items:
- Information Box: Custom text with
%tags and multi-line support. - Information Display: Custom HTML (supports
<b>,<i>,<u>,<color>,<backcolor>,<size>,<br>). - Challenge Pass Button: Required when operator response is required.
- Challenge Deny Button: Required when operator response is required.
- User Image: Displays the user’s photo or a custom image field.
- CCTV Stream: Live video from cameras associated with the challenged door(s).
- Challenge History: Live stream of past and present challenges.
- Browser Item: Displays a web page; user keywords can be used in the URL.
- Information Box: Custom text with
Configure Automatic Actions
- Click the Actions tab.
- Add Task Actions for each of the four events:
- On Challenge: Fires on every challenge occurrence matching the criteria.
- On Random Selection: Fires only on randomly selected challenges.
- On Allow: Fires when the operator clicks Allow.
- On Deny: Fires when the operator clicks Deny.
View a Challenge Definition
In System Designer:
- Click the Operator Challenge tab.
- Right-click the Challenge Definition and select View.
In GateKeeper:
- Click the Operator Challenge tab.
- Double-click the Challenge Definition (or select it and click View).
Verification
- Present a credential at a reader configured with Ask PC.
- Verify the Challenge dialog appears in the viewing application (System Designer or GateKeeper).
- Check Integriti Review for these messages:
Software Auth. Request— Card presented to a challenge-configured reader.Software Auth. Response— Operator allowed access.Software Auth. Denied— Operator denied access.Software Auth. Timeout— Operator did not respond within 20 seconds.Software Auth. Overflow— Another card was presented while waiting for a response.
- If using random selection, verify challenges appear at the expected frequency over multiple access attempts.
Troubleshooting
| Symptom | Resolution |
|---|---|
| Challenge dialog never appears | Ensure the Challenge Definition is open/viewed by an operator. Verify the reader and user both have Ask PC enabled. Check that at least one Door and one User are specified in the Challenge Definition. |
| Challenge appears for ALL users | Check Challenge Settings — Show Challenge To Operator may be set to Always instead of Only on Random Selection. |
| Access is granted without operator input | Check Requires Operator Input — if set to Never, the controller processes access based on permissions. |
| No Challenge Definition exists for the reader | Users with Ask PC will be granted access even if they normally lack permissions. Create a Challenge Definition to prevent this. |
| HTML formatting not displaying | Ensure angle brackets in text are escaped with double brackets (<< for <). |
Related Pages
- Integriti Operator Guide — Day-to-day GateKeeper operations.
- Integriti GateKeeper — Visitor and contractor management.
- Integriti Comms Tasks Automation — Task Actions reference.
- Integriti Communication Handlers — Comms task configuration.
- Integriti System Configuration — System Designer overview.