Skip to main content
Version: 11.5.0

Agent Identity

An agent identity is what HYPR AgentPass™ recognizes a request by. Every identity has an owner, the person responsible for the agent, so every request the agent sends is attributed both to the agent and to a person. All agent identities, local and cloud, are listed on the one Agents page.

Where Identities Come From​

An identity reaches the Agents page in one of these ways.

SourceHow it appearsIdentity it carries
Imported from a providerOn Agents, click Import agents, and click Sync beside a connected AI provider. Each provider key or agent becomes an identity, owned by the person it belongs to. See Import and Create AgentsThe provider key the agent uses
OnboardedA local agent that points at the gateway gains an identity when its first connection is approved. See Onboarding ModeIts owner's: the supervisor who onboarded it
Created as a cloud agentNew agent creates a cloud agent. See Cloud AgentsA gateway-issued credential. It acts for whoever is chatting with it
Created as a workload agentNew agent creates a workload agent, for work with nobody at the keyboard, such as automations, pipelines and cloud harnesses. See Workload AgentsIts own role and credential

Importing agents needs Agents: Sync, which Admin and Operator hold out of the box. For who can create agents, see Who Can Do What and the workload agent permissions.

Whose Access an Agent Carries​

An identity decides whose access the agent's requests carry. The Owner column on Agents shows it under the owner's name.

Shown asMeaning
Acts as ownerThe agent carries its owner's access, such as a local coding agent on the owner's machine
Acts as the chatting userThe agent acts for whoever is chatting with it, with that person's access
Acts with its own roleA workload agent. It carries the role assigned to it, not a person's

The Acts as filter on Agents separates agents that act for A person from Workload agents.

An agent that acts for a person uses that person's roles for MCP tools. See Controlling MCP Tool Access by Role. To reach a protected tool as its supervisor, an agent uses a scoped token the gateway holds. See Acting on Behalf of a Supervisor.

Find an Agent's Identity​

  1. Open Agents.
  2. Search by name, owner or the last characters of a key, or narrow the list with the filters. See Find an Agent.
  3. Click Details on the agent's row.

The details drawer's Overview shows the agent's provider, where it runs, whom it acts as, its owner, its key or external ID, when it was created or imported and from where, and its Agent ID. The Agent ID is what other pages ask for, such as a per-agent override for the session investigator. See Agent Details.

Any role with Agents: View can open the page. Admin, Operator, Security analyst and Auditor see every agent. Supervisor sees the agents they own or are assigned to.

Turning an Identity Off​

Turning an agent off stops its identity: the gateway refuses its requests until someone turns it back on. Turning an agent off also ends its live sessions. See Turning Off an Agent and Who Can Turn an Agent Off and On.