A group that uses SimpleAct as one organisation structures itself with sites. AI systems are assigned to a site, and the AI officer of a site sees and edits exactly its AI systems, including sub-units. That way responsibility for AI can be distributed locally without showing everything to everyone.

At a glance

Included from: Starter (AI inventory), beta
Where in the app: Administration → Users → Sites & AI officers
Output: Site hierarchy, assignment of AI systems, visibility per AI officer
Legal basis: Organisational responsibility for Art. 4 and Art. 26 AI Act
API: /api/v1/org-units

Sites

Sites form a hierarchy: each site can have a parent. The app refuses circular assignments.
Names are unique per organisation, regardless of upper and lower case.
Each AI system can be assigned to a site.
Sites also serve as the department of users. A site that is still the department of users can only be deleted once they have been moved.
Creating, renaming and deleting is up to administrators.

AI officers

You assign AI officers on the user, not on the site.

Visibility

An AI officer sees and edits all AI systems of the assigned sites including sub-units, in addition to individually granted systems, but no others.

Restricted access only

The assignment only takes effect for users with restricted AI system access. Administrators always see all AI systems and therefore cannot be assigned as a site AI officer.

"My site"

AI officers see their site in the app, so they know why they only see its AI systems.

Not group governance

Sites structure one organisation internally. Group governance, by contrast, links separate organisations.

AI officer is not a legal term

The AI Act does not prescribe an "AI officer". It does, however, require AI literacy of staff (Art. 4) and, for deployers, human oversight by competent persons (Art. 26(2)). An AI officer per site is one way to anchor this responsibility organisationally.