# Identity, users & access

> The dashboard's config views for who acts, whose credentials they use, and who is allowed to administer the platform.

Source: https://openap.org/docs/admin-identity

Three config views answer the identity questions: whose credentials an agent uses, which people are linked to
the platform, and who's allowed to administer it.

## Identity

**Identity** manages agent [identities and credentials](https://openap.org/docs/identity), and the [login providers](https://openap.org/docs/idp-signin)
people sign in through. Its two tabs — *Agent identities* (how agents authenticate to upstreams) and *Login
providers* (how humans sign in) — are the console view of `oap identity` and `oap idp`.

![Identity — agent identities, their credentials, and the login providers people sign in through.](https://openap.org/media/admin-identity.png)

## Users & Access

- **Users** — the people linked to the platform (via `oap user-identity`), and the credentials they've connected
  through the [self-service portal](https://openap.org/docs/managing-connections).
- **Access** — the platform admins and the SpiceDB [authorization schema](https://openap.org/docs/authorization) itself. Being an
  admin is a permission in the graph, so this is where you see and manage who holds it — the same graph every
  other check consults.
