Onboarding Mode
A connector's onboarding mode decides what HYPR AgentPass™ does the first time an unknown agent sends a request through that connector.
The Modes
Each mode handles a new agent's first request differently. The connector's Overview tab shows a short description beside each, and the create form shows a longer one.
| Mode | Console description | Effect on a new agent's first request |
|---|---|---|
| Require Approval | Agents need supervisor approval | The request is held. The agent's supervisor approves or denies it from the HYPR mobile app or the console. Approval grants access for a limited time |
| Observe only | Record unmanaged client activity (shadow AI) — never block or onboard | The request is recorded and forwarded, without onboarding the agent. Use it to see what is already in use before you enforce anything. See Desktop Activity |
| Disabled | Self-service onboarding is off | The request is forwarded without identifying or onboarding the caller, so the traffic is not attributed to an agent |
Choose Require Approval to put every new agent in front of its supervisor, and Observe only to see your traffic first. Choose Disabled only for a connector whose traffic you do not need to attribute.
Set the Mode
You need Connectors: Edit to change the mode. Admin has it.
- Open the connector, on its Overview tab.
- Under Onboarding Mode, select a mode. The change saves at once, and Onboarding mode updated confirms it.
On an AI provider connector, you also choose the mode on the create form's last step.
Where the Mode Applies
The mode takes effect on AI provider connectors. Each kind starts from its own default.
| Connector | Default | How the mode applies |
|---|---|---|
| Anthropic, OpenAI | Require Approval | Every mode applies |
| AWS Bedrock, AWS Bedrock Mantle | Observe only | Require Approval becomes available once the connector has identity enrichment |
| Microsoft Foundry | Observe only | Require Approval holds developers who sign in with Entra ID |
| Custom AI provider | Require Approval | The connector uses the mode for Observe only attribution, and forwards every request |
| Cloud agent and channel connectors | Disabled | These connectors identify their callers in their own way, so the mode leaves their requests unchanged |
| REST API connectors | — | The gateway serves the API's tools itself, so the mode leaves their requests unchanged |
The Onboarding Mode card appears on every connector except MCP server connectors. For the Custom AI provider, see Custom AI Provider.
AWS Bedrock and AWS Bedrock Mantle need identity enrichment, an IAM role or an access key, before they accept Require Approval. Until then, the option is unavailable, and hovering over it shows Needs identity enrichment. Add it in Edit. See AWS Bedrock.
On AWS Bedrock Mantle, you choose Require Approval on the create form's last step, or later on the connector's Onboarding Mode card. It is tested with Claude Code and Codex, and a developer who has just signed in to AWS waits about 2 minutes to be identified. See AWS Bedrock Mantle.
On Microsoft Foundry, Require Approval holds developers who sign in with Entra ID. Resource-key, application and managed-identity callers are recorded, and never held. See Onboarding New Developers.
Timeouts and Validity
Three tenant-wide values, under Settings → Gateway settings → Approvals, shape how Require Approval behaves.
| Setting | What it bounds |
|---|---|
| Onboarding approval timeout | How long a held first request waits for a supervisor before it expires |
| Policy-triggered approval timeout | The same wait, for a request held by a policy |
| Onboarding access validity | How long an approved agent keeps access before it is held again |
See Gateway Settings for the tab.
Related
- Onboarding Your Agent — the supervisor's side of a held first request
- Approving and Denying Agent Actions — what arrives on the phone and what each answer does
- Desktop Activity — where Observe only traffic is listed