Skip to main content
Version: 11.5.0

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 canWhere it is covered
Connect console sign-in to your identity provider, and change Settings → Gateway settingsSigning 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 useRoles and Permissions, Controlling MCP Tool Access by Role
Add, edit, turn on and off, and delete connectorsConnectors
Create cloud and workload agents, issue workload credentials, and turn any agent off and onWorkload Agents, Who Can Turn an Agent Off and On
Write, test, promote and delete every policyWhat Your Role Lets You Do
Deny or revoke any request, approve another supervisor's onboarding request, and delete pending requestsWho Can Answer
Connect your HYPR tenant, and set up push notifications for supervisors' phonesConnecting to Your HYPR Tenant, Notifications
Enroll workstations, and configure the AI tools on them under DesktopsGetting Started with Desktops
Run access reviewsRunning Agent Access Reviews
Contain agents, change guardrail settings, run the Proving Ground and govern judgesWho Manages Guardrails
Set data retention, export destinations and data classificationData 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 Admin Before You Turn On SSO

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​

  1. Sign in with the recovery administrator from your invitation. See Sign In for the First Time.
  2. Fill in and save your identity provider settings, including Role claim, but leave Enable SSO off. See Connect the Console to Your Identity Provider.
  3. 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.
  4. Turn on Enable SSO, sign out, and sign in with SSO. Your name at the top right shows Admin.
  5. Add an AI provider connector, and keep its onboarding mode on Require Approval. See Add a Connector and Onboarding Mode.
  6. 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.
  7. Connect your HYPR tenant, set up push delivery, and send a test push. See Connect the Tenant and Send a Test Push.
  8. Onboard one agent, and approve its first connection. See Onboarding Your Agent.
  9. Create a policy in Observe mode, check its decisions, then promote it to Enforce. See Open the Wizard and Promote.
  10. 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 toGo to
Follow the full rollout, including day-to-day operation and offboardingQuick Start: Administering HYPR AgentPass
Implement a complete use caseAgentPass Playbooks
Bring workstation AI tools under the gatewayGetting Started with Desktops
Give a scheduled job or pipeline its own identityWorkload Agents
Review which agents still need their accessRunning Agent Access Reviews
Hold sensitive agent actions with guardrailsInput Guardrails
Decide what the gateway keeps, and where records goData Management

Guardrails, Conversations and Access reviews carry a Preview tag in the console.