Identity
Every request through HYPR AgentPass™ is attributable. The gateway knows which agent sent it and which person is responsible for that agent. When the agent reaches a tool as that person, the gateway also knows the scope. Three identities make that possible.
| Identity | What it proves | How it is issued | Where you manage it |
|---|---|---|---|
| Agent identity | Which agent sent the request | A gateway-assigned credential, created in the console or synced from a connected provider | Oversight → Agent identities |
| Supervisor identity | Which person is responsible for the agent | Console sign-in through your identity provider, or directory provisioning | Oversight → People |
| Acting on behalf of a supervisor | That the agent may reach a tool as its supervisor, within a scope | A scoped token the gateway holds and the agent never handles | Per connector, on its Connections tab |
An identity's role decides what it may do. Groups decide which people can use a shared agent.
Related
- Roles and Permissions — what a role grants, and how people get one
- Identity and Token Model — how the three identities relate on one request