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 credential imported from a connected provider, created when a local agent is onboarded, or issued when you create a cloud or workload agent | Agents |
| Supervisor identity | Which person is responsible for the agent | Console sign-in through your identity provider, or directory provisioning | People, on the Users tab |
| 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 |
A person's roles decide what they may do in the console, and which MCP tools their agents may use. A workload agent carries a role of its own. 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