A Restricted Visitor list — a watchlist of people who should be flagged or barred at entry — is one of the most useful controls a site has. But its value depends entirely on how well it is managed. A stale, inaccurate or unaccountable list creates as many problems as it solves.
What belongs on the list
Typically: individuals previously involved in a security incident, people formally barred, or those a site has a documented reason to stop. The bar for adding someone should be clear and consistent — see the feature basics in Restricted Visitor, explained.
Govern it properly
- Define who can add or remove entries, and require a reason.
- Record who added an entry and when, for accountability.
- Review periodically so the list does not go stale.
- Have a route to correct or remove an entry that is wrong.
Act on a match, humanely
When a visitor matches, the system should flag it at the point of verification, before they reach the desk — but the response should involve a person, not an automatic confrontation. A flag is a prompt to handle a situation carefully, not a verdict.
Fairness and privacy
A watchlist holds sensitive judgements about people, so it must be accurate, purpose-limited and governed — consistent with DPDP principles and basic fairness. Confirm your approach with your own compliance function.
Restricted Visitor with Certopact
Certopact Access screens visitors against your Restricted Visitor list at check-in — and, in India, Certopact Entry can flag a matched identity before a badge ever prints.