ExampleEditorialv1.0.0

Facial recognition at access control: the guard behind the camera counts too

An organisation secures the entrances to its buildings with facial recognition and uses that biometric access control to register visitors as well. When the system returns no match, a security officer reviews the camera images and decides personally whether someone may enter. The question is whose measures have to reach that officer: those of the supplier of the model, those of the department that deploys the system, or both.

The official source remains authoritative. This is general information about obligations and not legal advice. See this object on the map

Address and citation

This object has an address of its own that is never renamed or reused. Store the identifier in your own file, not the title or the link.

Identifier: praxikon:eu:ai-act:example:example-artikel-4-gezichtsherkenning-toegangscontrole
Payload hash (sha256): 595c5cc236618a40fa4882c79603f0febc9762b4165cdf0ac60b70bdbbe5c457

Citation line

Praxikon, "Facial recognition at access control: the guard behind the camera counts too", praxikon:eu:ai-act:example:example-artikel-4-gezichtsherkenning-toegangscontrole@1.0.0, dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.1.0 (schema 1.4.0), effective_at 2026-08-08T00:00:00.000Z, known_at 2026-08-14T00:00:00.000Z, sha256 595c5cc236618a40fa4882c79603f0febc9762b4165cdf0ac60b70bdbbe5c457

Version: 1.0.0
Legal time (effective_at): 1 August 2024
Knowledge time (known_at): 8 August 2026
Closed on: Not closed
Topics: examples

Review status: Placed against the official source (8 August 2026). Next check due by 4 February 2027. The check date is the knowledge date of this version; no later recheck has been recorded.

What this object links to

Every relation appears below as a path: from the source with its locator, through the conditions and exceptions of the object carrying the relation, to the consequence. A locator belongs to a statement in the data and not to a relation, so the source is the source anchor of the carrying object.

The obligation this hangs off

1 of 1 shown

The object belongs to this obligation. The source line it hangs off sits there.

Source
Official fact on this object, with its locator.
- EU Artificial Intelligence Act 2024/1689
  Locator: Article 4(1)
  praxikon:eu:ai-act:source:reg-eu-2024-1689
  Open official source
Via
No condition or exception recorded on this object.
Consequence
- ObligationArticle 4: AI literacy
  praxikon:eu:ai-act:obligation:article-4-ai-literacy

What this object is about

2 of 2 shown

The object is about this role. Undifferentiated: it does not follow that the duty rests on this role.

Source
Official fact on this object, with its locator.
- EU Artificial Intelligence Act 2024/1689
  Locator: Article 4(1)
  praxikon:eu:ai-act:source:reg-eu-2024-1689
  Open official source
Via
No condition or exception recorded on this object.
Consequence
- ActorDeployer
  praxikon:eu:ai-act:actor:deployer
- ActorProvider of an AI system
  praxikon:eu:ai-act:actor:provider

What this object states

Official fact

Attributable to a named primary source, with a locator. Where they differ, the official source prevails.

Article 4(1) provides that providers and deployers of AI systems shall take measures to support the development of AI literacy of their staff and other persons dealing with the operation and use of AI systems on their behalf. In doing so they must take into account technical knowledge, experience, education and training and the context the AI systems are to be used in, and consider the persons or groups of persons on whom the AI systems are to be used. The same provision states that this obligation does not require providers or deployers to guarantee any specific level of AI literacy of any individual.
- Locator: Article 4(1)praxikon:eu:ai-act:source:reg-eu-2024-1689Open official source

Our interpretation

Our own reading. It can change without the law changing, and it is not the position of a supervisory authority.

We read the phrase about the persons on whom the system is used as the centre of gravity for biometrics: whoever stands in front of the camera is subject to the outcome and has little to set against it. That argues for equipping the officer who decides for himself when no match comes back more substantively than the colleague who merely switches the system on and off. The article itself names no sufficient level and expressly states that you need not guarantee one, so where the floor lies for each role stays open. In our assessment a record kept per role, stating the choice made and the reason for it, is easier to defend than one organisation-wide session backed only by an attendance list.
- Locator: Article 4(1)praxikon:eu:ai-act:source:reg-eu-2024-1689Open official source

When this applies

No condition recorded on this object.

When this does not apply

No exception recorded on this object.

Referring to this object

Citation block

Copy this reference into your advice, article or file. The identifier, the version and the hash keep the statement findable later, even once the dataset has moved on.

Reference

Praxikon, "Facial recognition at access control: the guard behind the camera counts too",
praxikon:eu:ai-act:example:example-artikel-4-gezichtsherkenning-toegangscontrole@1.0.0,
dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.1.0 (schema 1.4.0),
effective_at 2024-08-01T00:00:00.000Z, known_at 2026-08-08T00:00:00.000Z,
sha256 595c5cc236618a40fa4882c79603f0febc9762b4165cdf0ac60b70bdbbe5c457,
https://www.praxikon.com/en/verkenner/example/example-artikel-4-gezichtsherkenning-toegangscontrole
(https://www.praxikon.com/api/v1/entities?id=praxikon%3Aeu%3Aai-act%3Aexample%3Aexample-artikel-4-gezichtsherkenning-toegangscontrole&effective_at=2024-08-01&known_at=2026-08-08&lang=en, accessed 2026-08-25)

Short form

praxikon:eu:ai-act:example:example-artikel-4-gezichtsherkenning-toegangscontrole@1.0.0 (sha256 595c5cc2)

BibTeX

@misc{praxikon-eu-ai-act-example-example-artikel-4-gezichtsherkenning-toegangscontrole-1-0-0,
  author       = {{Praxikon}},
  title        = {Facial recognition at access control: the guard behind the camera counts too},
  year         = {2026},
  version      = {1.0.0},
  number       = {praxikon:eu:ai-act:example:example-artikel-4-gezichtsherkenning-toegangscontrole},
  howpublished = {AI Act Change \& Evidence Graph, dataset 2.1.0, schema 1.4.0},
  note         = {effective_at 2024-08-01T00:00:00.000Z; known_at 2026-08-08T00:00:00.000Z; sha256 595c5cc236618a40fa4882c79603f0febc9762b4165cdf0ac60b70bdbbe5c457},
  url          = {https://www.praxikon.com/en/verkenner/example/example-artikel-4-gezichtsherkenning-toegangscontrole},
  urldate      = {2026-08-25},
  language     = {en}
}

CSL JSON

[
  {
    "id": "praxikon:eu:ai-act:example:example-artikel-4-gezichtsherkenning-toegangscontrole@1.0.0",
    "type": "dataset",
    "title": "Facial recognition at access control: the guard behind the camera counts too",
    "container-title": "AI Act Change & Evidence Graph",
    "publisher": "Praxikon",
    "version": "1.0.0",
    "number": "praxikon:eu:ai-act:example:example-artikel-4-gezichtsherkenning-toegangscontrole",
    "URL": "https://www.praxikon.com/en/verkenner/example/example-artikel-4-gezichtsherkenning-toegangscontrole",
    "language": "en",
    "issued": {
      "date-parts": [
        [
          2026,
          8,
          8
        ]
      ]
    },
    "accessed": {
      "date-parts": [
        [
          2026,
          8,
          25
        ]
      ]
    },
    "note": "dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.1.0; schema 1.4.0; effective_at 2024-08-01T00:00:00.000Z; known_at 2026-08-08T00:00:00.000Z; sha256 595c5cc236618a40fa4882c79603f0febc9762b4165cdf0ac60b70bdbbe5c457; retrieved_from https://www.praxikon.com/api/v1/entities?id=praxikon%3Aeu%3Aai-act%3Aexample%3Aexample-artikel-4-gezichtsherkenning-toegangscontrole&effective_at=2024-08-01&known_at=2026-08-08&lang=en; licence https://www.praxikon.com/nl/legal/terms"
  }
]

How to verify a reference later is set out in the methodology. Terms

For agents and integrations

This page and the machine output come from the same object and the same two time axes.

Open as JSON Open as JSON-LD Read the methodology