Your First Governed Agent
This page takes one agent through HYPR AgentPass™ end to end, so you can see what the gateway does with its traffic. Each section links to the guide that covers the task in full.
Keep the first run small: one connector, one agent and one supervisor. By the end you have a request you can find in the log and an approval you answered. Add breadth afterwards.
Start Here by Role
The sections on this page are for the administrator setting up the gateway for the first time. If that is not your job, start with the guide for your role.
| You are | Start with |
|---|---|
| An administrator setting up the gateway | The sections on this page, in order, or Get Started as an Administrator for a shorter path |
| An operator running the gateway day to day | Get Started as an Operator |
| A security analyst triaging alerts and investigating agents | Get Started as a Security Analyst |
| An auditor collecting evidence | Get Started as an Auditor |
| The owner of the models guardrails consult | Get Started as a Model Governance Owner |
| A supervisor of one or more agents | Get Started as a Supervisor |
| A developer using a coding agent on a work computer | Get Started as a Developer |
| Someone chatting with agents in the Agent Portal | Get Started with the Agent Portal |
To implement a complete use case instead, pick one of the AgentPass Playbooks.
Check What You Need in Place
Settle the gateway's public origin first. Connectors and identity providers are configured against it.
Confirm you have:
- The gateway's public origin, reachable from outside your network
- An OpenID Connect provider you can register an application with
- Whatever your chosen connector needs on its own side
Sign In and Connect Your Identity Provider
Your first sign-in uses the recovery administrator account from your invitation. Console access for everyone else comes from your own identity provider, and you configure it in the console itself. Do this before you invite anyone else, so they arrive to a working sign-in.
You will:
- Sign in with the recovery administrator
- Register the console's redirect URI with your provider
- Enter the issuer URL and client credentials, and choose the claim that carries roles
- Leave Enable SSO off until the next section is done
Go to Sign In for the First Time →
Give the People Involved Roles
A role decides what someone can do in the console and which tools their agents may use. A new tenant maps no identity provider values to roles, so everyone who signs in with single sign-on (SSO) gets the default role, Supervisor. Map your administrators to Admin before you turn on SSO, or your own SSO sign-in opens as a Supervisor too.
You need at least one supervisor before you can onboard an agent, because onboarding waits for a supervisor's approval.
You will:
- Map your identity provider's values to roles, starting with Admin
- Turn on Enable SSO, and sign in with it to confirm you work as Admin
- Choose which tools each role's agents can use, if agents will call MCP servers or REST APIs
Go to Map Identity Provider Values to a Role →, then Set Which Tools a Role Can Use →
If your SSO sign-in opens as a Supervisor, sign out and sign in again with the recovery administrator. See Get Started as an Administrator.
Add One Connector
A connector is a target you bring under the gateway. Pick the one your first agent needs, and leave the rest for later.
You will decide:
- Which kind matches your target: an AI provider, an MCP server, a REST API, a cloud agent or a channel
- Which provider-side setup that kind requires first
These connectors have full walkthroughs:
- AI providers: Anthropic, OpenAI, AWS Bedrock and AWS Bedrock Mantle
- Microsoft 365 Copilot
- Provider-managed cloud agents: Anthropic and AWS Bedrock AgentCore
Set Up a Supervisor's Approval Passkey
Supervisors can answer approvals on a phone, with a passkey. When your organization requires signed approvals, the passkey must exist before an agent can be approved. If you are also the supervisor, set up your own first.
You will:
- Connect the gateway to your HYPR tenant, once, as the administrator
- Turn on push delivery, so approval requests reach phones
- Install the HYPR app and sign in
- Enroll a passkey from the gateway on your phone
Go to Connecting to Your HYPR Tenant →, then Configure Push Delivery →, then Setting Up Your Approval Passkey →
Onboard Your First Agent
Point one agent at the gateway. Its first request is held for approval instead of passing straight through. That hold is what you are here to see. The hold needs the connector's onboarding mode set to Require Approval, the default for Anthropic and OpenAI connectors. An AWS Bedrock connector starts in Observe only.
You will:
- Point the agent at the gateway URL
- Approve its first connection
Find the Request in the Log
The Request Log shows the traffic your agent just sent. Each entry is attributed to the agent and shows the model it used and how the request ended.
You will:
- Filter the live stream to your one agent
- Inspect a single request
Go to Viewing the Request Log →
Make One Action Need a Person
Onboarding holds an agent once. A policy holds it again for the specific actions you care about.
You will:
- Create one policy and associate it with your connector
- Have the agent attempt the action, then answer the approval on your phone
You can also describe the rule in plain English and let the gateway draft it. See Authoring a Policy with AI →. That path needs a drafting model configured first, in Setting Up AI Authoring.
To see what arrives on the phone and what each answer does to the agent, go to Approving and Denying Agent Actions →.
When the held action goes ahead after you approve it, and its request shows in the Request Log against your agent, your first agent is governed end to end.
Where to Go Next
With one agent working end to end, choose your next direction.
| If you want to | Go to |
|---|---|
| Implement a complete use case, step by step | AgentPass Playbooks |
| Govern what the model may be asked or told | Governing Inference Traffic |
| Limit which tools a role's agents may call | Controlling MCP Tool Access by Role |
| Understand how agents, supervisors and delegation are identified | Identity |
| Give a non-human caller its own identity | Workload Agents |
| See the AI tools already in use on your fleet | Desktop Activity |
| Keep workstation agents on the gateway | Enforcement Points |
| Control what the gateway retains | Data Management |
Related
- HYPR AgentPass: Overview — what AgentPass does, and a start-here guide for each role
- HYPR AgentPass: How It Works — the request path these sections assemble
- Prerequisites — the full list behind the first section