Get Started as an Administrator
Role: Admin. The console shows the role you work in beside your name, at the top right.
Who This Is For
You set up and run your organization's HYPR AgentPass™ tenant: who signs in, which providers and tools agents reach, and the rules agents follow.
In the console, Home opens with Set up AgentPass, a guide that tracks your first setup step by step. See The Setup Guide.
Admin holds every permission in the console. It is locked, so its name and permissions never change, and your tenant always keeps a role that can administer it. If your organization gives administrators a custom role instead, your access can differ from this page.
What You Can Do
| You can | Where it is covered |
|---|---|
| Connect console sign-in to your identity provider, and change Settings → Gateway settings | Signing In to the Console, Gateway Settings |
| Assign roles, create custom roles, map identity provider values to roles, and choose which tools each role's agents can use | Roles and Permissions, Controlling MCP Tool Access by Role |
| Add, edit, turn on and off, and delete connectors | Connectors |
| Create cloud and workload agents, issue workload credentials, and turn any agent off and on | Workload Agents, Who Can Turn an Agent Off and On |
| Write, test, promote and delete every policy | What Your Role Lets You Do |
| Deny or revoke any request, approve another supervisor's onboarding request, and delete pending requests | Who Can Answer |
| Connect your HYPR tenant, and set up push notifications for supervisors' phones | Connecting to Your HYPR Tenant, Notifications |
| Enroll workstations, and configure the AI tools on them under Desktops | Getting Started with Desktops |
| Run access reviews | Running Agent Access Reviews |
| Contain agents, change guardrail settings, run the Proving Ground and govern judges | Who Manages Guardrails |
| Set data retention, export destinations and data classification | Data Management, Data Classification |
Someone else does this: each agent's supervisor approves the actions a policy holds for that agent. You can deny or revoke those requests, but only the agent's supervisor can approve them.
How It Works for You
Your first sign-in uses the recovery administrator account from your invitation. It works as Admin, and it stays on the sign-in page as a way back in if single sign-on (SSO) is unavailable.
Everyone else signs in with SSO. At each sign-in, AgentPass gives a person the roles their identity provider values are mapped to. A new tenant has no mappings, so anyone without a mapped value gets the default role, Supervisor. That includes you, until you map the value that identifies your administrators to Admin.
Map your administrators' identity provider value to Admin before you turn on Enable SSO. Otherwise your first SSO sign-in opens the console as a Supervisor, with no Settings and no Roles.
If that happens, click your name at the top right, and click Sign out. The sign-in page keeps the recovery administrator form under or recovery administrator. You can also reach that page at /login on your gateway's address. Sign in with the recovery administrator, add the mapping, then sign in with SSO again.
After setup, keep the recovery administrator credentials in a protected break-glass location.
Your First Hour
- Sign in with the recovery administrator from your invitation. See Sign In for the First Time.
- Fill in and save your identity provider settings, including Role claim, but leave Enable SSO off. See Connect the Console to Your Identity Provider.
- Map your administrators' value to Admin, and map other values to Operator, Supervisor or the other roles. See Map Identity Provider Values to a Role.
- Turn on Enable SSO, sign out, and sign in with SSO. Your name at the top right shows Admin.
- Add an AI provider connector, and keep its onboarding mode on Require Approval. See Add a Connector and Onboarding Mode.
- If agents will call MCP servers or REST APIs, add those connectors, and choose which tools each role's agents can use. See Set Which Tools a Role Can Use.
- Connect your HYPR tenant, set up push delivery, and send a test push. See Connect the Tenant and Send a Test Push.
- Onboard one agent, and approve its first connection. See Onboarding Your Agent.
- Create a policy in Observe mode, check its decisions, then promote it to Enforce. See Open the Wizard and Promote.
- Find your agent's requests in Activity → Request log. See Filter the Stream.
When the Request Log shows requests attributed to your agent, the gateway is governing its first agent. Your First Governed Agent walks the same path with more context for each stage.
Where to Go Next
| If you want to | Go to |
|---|---|
| Follow the full rollout, including day-to-day operation and offboarding | Quick Start: Administering HYPR AgentPass |
| Implement a complete use case | AgentPass Playbooks |
| Bring workstation AI tools under the gateway | Getting Started with Desktops |
| Give a scheduled job or pipeline its own identity | Workload Agents |
| Review which agents still need their access | Running Agent Access Reviews |
| Hold sensitive agent actions with guardrails | Input Guardrails |
| Decide what the gateway keeps, and where records go | Data Management |
Guardrails, Conversations and Access reviews carry a Preview tag in the console.
Related
- Permissions by Role — every permission each role holds, by product area
- Get Started as an Operator — the role that runs the gateway day to day
- Get Started as a Supervisor — what reaches the people who supervise agents
- Finding Your Way Around the Console — which pages each permission shows