Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.
Version: 11.3.0

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 Four 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.

ModeConsole descriptionEffect on a new agent's first request
Require ApprovalAgents need supervisor approvalThe 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
Auto ApproveAgents are approved automaticallyPolicies still apply
DisabledSelf-service onboarding is offThe connector does not hold or onboard new agents
Observe onlyRecord unmanaged client activity (shadow AI) — never block or onboardThe request is recorded and forwarded, without onboarding the agent. Use it to see what is already in use before you enforce anything. See Discovering Unmanaged Agents

Set the Mode​

  1. Open the connector, on its Overview tab.
  2. 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. Changing the mode needs permission to edit connectors.

The Onboarding Mode card appears on every connector except MCP server connectors. The mode takes effect on Anthropic, OpenAI, AWS Bedrock and AWS Bedrock Mantle connectors. A Custom AI provider connector uses it only for Observe only attribution, and never holds or refuses a request.

AWS Bedrock and AWS Bedrock Mantle do not offer Auto Approve. Both need identity enrichment, an IAM role or an access key, before they accept Require Approval. See Connecting AWS Bedrock.

On AWS Bedrock Mantle, you choose Require Approval on the create form's last step. 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 Connecting AWS Bedrock Mantle.

Timeouts and Validity​

Three tenant-wide values, under Advanced → Gateway Settings → Approvals, shape how Require Approval behaves.

SettingWhat it bounds
Onboarding approval timeoutHow long a held first request waits for a supervisor before it expires
Policy-triggered approval timeoutThe same wait, for a request held by a policy
Onboarding access validityHow long an approved agent keeps access before it is held again

See Gateway Settings for the tab.