Skip to main content

Define locations and restricted zones

Beyond buildings and floors, two location layers drive the visit workflows: localisations, the precise destinations visits point to, and restricted zones (ZRR), whose access is regulated and validated.

Manage localisations

  1. Open Hamilton Visitor, click Administration, then "Localisations management" in the Places section.

  2. Click Add and fill in the form — errors guide you:

    • Localisation name (mandatory, unique — "is already used" otherwise).

    • Site (mandatory).

    • Optional details such as the external system identifier and the room/cage reference.

  3. Validate.

Visit requests carry a localisation; the validation screen even warns when a request has no localisation attached ("Warning, the access request has no associated localisation").

Manage restricted zones (ZRR)

  1. In the Places section, click "ZRR management".

  2. Maintain the restricted zones. A localisation belonging to a ZRR triggers the reinforced validation path: nationality checks, enquiries, access authorizations (CPPA) and, for derogations, exceptional passes (LPE).

The user-side screens of this workflow are described in "Manage restricted zone access and exceptional passes" and "Validate visits and manage access requests" in the user guides; the rules themselves are configured in "Define visit validation rules and validator groups".

Good to know

  • Visit statistics break down by localisation and by ZRR — precise locations make precise reporting.

  • The ZRR and CPPA menus only appear on sites operating restricted zones (feature-dependent).

Did this answer your question?