# ID document OCR for access-control workflows

Source: https://idscanly.com/access-control/
Language: en

DOCUMENT OCR FOR YOUR WORKFLOW

Prepare visitor records from supported identity documents while keeping admission rules in your access system. IdScanly helps staff review the person’s details before issuing a pass.

[Discuss this integration](https://idscanly.com/contact/?useCase=access-control) [Try the live demo](https://idscanly.com/live-demo/)

![Original illustration of the document workflow for Access control](https://idscanly.com/images/use-cases/access-control-1200.webp)

Access control

## Visitor registration before a pass is issued

Reception teams may retype visitor details from a document into a registration system and then again into a badge tool. OCR can support a draft visitor record without automating the decision to admit someone.

## Booked visits and walk-in examples

### A pre-registered appointment

The visitor arrives for a scheduled meeting. Reception compares the extracted name with the invitation and confirms host and time; the access system makes the admission decision.

### An unplanned visitor at reception

Create a draft visitor entry from permitted supported fields. Contact the proposed host and confirm the visit before issuing any badge; an OCR response must not open a door.

## Reception review before admission

1. ### Explain visitor registration
   
   Explain the visitor-registration purpose and capture only the permitted document data.
2. ### Attach the host and visit
   
   Send the extracted fields to a draft visitor entry linked to the host or appointment.
3. ### Confirm admission separately
   
   Confirm the visitor, appointment and required checks before issuing a badge or opening access.

## A visitor record linked to a host

Visitor name, document type and selected identifiers only when necessary for your site’s access policy.

[Read the API documentation](https://idscanly.com/developers/)

## Visitor data stays purpose-limited

Separate visitor logs from staff identity files. Decide who may search past visits and avoid carrying document fields into badge printing when they are unnecessary.

Keep document extraction separate from the access decision and avoid retaining identification details longer than the site’s lawful policy requires.

[Privacy Policy](https://idscanly.com/privacy/)

## Access-control OCR questions

Does OCR recognise a face or unlock a gate?

No. OCR returns document fields. Face comparison, biometrics, watch-list checks, badge issuance and door-control actions belong to separate systems.

Does reading an ID issue a badge?

No. Badge issuance and door control need separate access-system logic and authorisation.

Should the badge display the document number?

Usually the badge needs a visitor name and visit reference, not all extracted identifiers. Define the minimum for your site.

What if the visitor has no supported document?

Offer your site's alternative registration and security-review process rather than interpreting extraction failure as an admission verdict.

Access control

## Discuss this integration

[Discuss this integration](https://idscanly.com/contact/?useCase=access-control)

## Related use cases

[Hotels & hospitality](https://idscanly.com/hospitality/) [Fintech](https://idscanly.com/fintech/) [Car & mobility rental](https://idscanly.com/car-rental/) [Property rental](https://idscanly.com/property-rental/) [KYC & onboarding](https://idscanly.com/kyc-onboarding/)