Define the validation rules
Open Hamilton Visitor, click Administration, then "Rules management" in the Visit validation section.
Click Add and fill in the rule form. The form guides you with mandatory-field, uniqueness and format checks.
A rule combines the conditions (visit type, localisation, visitor nationality or status, documents...) with the effect: the visit request enters the validation list instead of reaching reception directly.
Validate.
Define the CPPA rules
For sites with restricted zones (ZRR), the "CPPA rules" screens define the access authorization regime: which zone requires which authorization level, and the conditions (nationality, enquiry) attached. These rules power the "Access authorizations" screen used at the desk — see "Manage restricted zone access and exceptional passes" in the user guides.
Manage validator groups
In the Visit validation section, click "Validator groups management".
Compose the groups of people who arbitrate the requests, per scope. Members get the Validation menu with the pending list and the decision actions (OK, to accompany, notify management, waiting, incomplete, forbidden) — see "Validate visits and manage access requests" in the user guides.
The "direction" right (rights groups) marks the management level involved in the "notify management" decisions.
Verify the workflow
Pre-register a test visit matching a rule: it appears in the validation list, not in reception's expected visits.
As a validator, approve it: it reaches the pre-registrations list; refuse another to confirm the requester is informed.
Good to know
The automatic arbitration engine pre-assesses requests where the rules allow it ("No validation required" / "Not arbitrated"); the Recalculate action re-runs it after a rule change.
Document requirements (and their renewals) plug into the same decisions — see "Manage document types and renewals".