AgentPass Playbooks
AgentPass playbooks walk through a complete use case in order, and each step links to the page that owns the detail. Pick the one that matches your goal.
| Playbook | For | Ends with |
|---|---|---|
| Quick Start: Administering HYPR AgentPass | The Admin who rolls out AgentPass, from the first sign-in to running it day to day | Your team signing in with single sign-on and mapped roles, agents reaching models and tools only through the gateway, and policies that observe before they enforce |
| See and Govern the AI Tools Already on Your Workstations | IT and security administrators who need visibility and control over the AI tools on company workstations | Every workstation AI tool attributed to a user and device, routed through the gateway, and unable to bypass it |
| Give a Team Governed Coding Agents | Administrators rolling out coding agents, such as Claude Code, to a development team | Each developer's agent held for a supervisor's approval, offered only the tools its role permits, and attributed in the Request Log |
| Require a Person for High-Value Agent Actions | Security and platform teams who want routine work to run on its own while named sensitive actions wait for a person | Chosen actions held until a supervisor approves them, each approval bound to that person and action |
| Respond to an Agent Incident | Security analysts handling an agent incident, working with an Admin for configuration changes | The agent stopped or released, what it did understood, the alert closed with a note, and the evidence exported |
| Using AI Tools with HYPR AgentPass | Employees whose AI tools run through AgentPass, including developers and Agent Portal users, and the administrators who hand the guide out | Each place employees use AI set up, and every AgentPass notice understood |
For a first hour in your own role, rather than a full use case, see the start-by-role guides on the HYPR AgentPass: Overview.
The Playbooks index lists AgentPass playbooks alongside the playbooks for other HYPR products.