> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# People and members administration

> Administer expertise tags and start workforce integrity audits, and read the deployment's person-identity check, with a platform API key.

These admin routes run the Console's own workforce operations for a platform API key. An External App is refused with `403`, even when it holds the permission.

* Expertise tags: list them with `workforce:read`; create or update one with `workforce:manage`.

* Workforce integrity: start an audit with `workforce:manage`; read a run, with its counts and summaries, and list its findings five at a time, with `workforce:read`. A finding answers its invariant, classification, status, decision and the ids it affects; its key, evidence, resolved names, proposed repair and decision reason stay in the Console, since they can name a person.

* The deployment's person-identity integrity check: its status, counts and staleness, with `workforce:read`.

* Worker seats: deactivate a seat with `org:manage`; read and set a worker's expertise levels with `workforce:read` and `workforce:manage`.

* Memberships: update a membership's role and remove a member with `org:manage`.

Each seat and membership route applies the person-reach rule: a machine caller cannot reach a person seated in a customer organization. A seat or membership whose person is out of reach answers `404`, the same as one that does not exist, and a write to it changes nothing. A position member is in reach only when every worker assigned to it is; a position with 100 or more active assignees is too many to decide, and the membership routes answer `409 conflict` for it whatever its members. Creating people and listing a unit's members are not on the API yet.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.