# People and access (admin)

> For administrators: give people roles on the Probe server, and understand how board visibility is governed by Trace project access.

_Source: E-Sharp (esharp.se) · Probe guide_


*This page is for the administrator.*

You control who has access to Probe and what they see. Sign-in is through your own identity provider (see [account and SSO](/en/probe/support/account-and-sso)).

## Roles

You can give a person a role on the server, adding the person first if they have no account. Assigning roles itself requires the right permission (AssignRoles). A person is matched on name, email or directory subject.

## Board visibility via Trace

Which boards a person sees is governed by **Trace project access** per person — Probe and Trace federate. A board a person doesn't have access to **answers as non-existent** to them; they aren't even told it exists. That's deliberate: visibility shouldn't leak through an "access denied".

## Seats

The role decides what you may do; the seat decides review versus viewing — see [seats, licence and fleet](/en/probe/support/seats-licence-and-fleet).

---

Related: [API access and keys](/en/probe/support/api-access-and-keys) and [change log and audit](/en/probe/support/change-log-and-audit).

*Probe is E-Sharp's design-review engine.*
