Skip to main content
Version: 11.5.0

Platform: Configuration

Overview​

On Platform: Configuration, a platform administrator sets the fleet-wide defaults for configuring desktop AI agents in HYPR AgentPass™. These are the default configuration, and the block-host lists every organization inherits until it sets its own. With a good default, each organization has sensible coverage as soon as it turns on Configure agents from AgentPass, without configuring anything first.

note

Editing the platform defaults is a control-plane task for platform administrators, who need permission to view and manage organizations across the platform. It is separate from the settings a tenant administrator edits in Desktops → Desktop configuration → Configuration. See Agent Configuration.

Open Platform: Configuration​

Open Platform: Configuration from the navigation. It appears with the other platform pages, such as Tenants and Platform: Observation, for administrators who can view organizations across the platform. The page holds two things: the default configuration, and the fleet block-host lists.

Set the Default Configuration​

The top of the page is the configuration editor a tenant administrator sees, without the Configure agents from AgentPass switch and without a choice of connector. Each organization makes both decisions for itself, because connectors belong to an organization. What you set here is served to every organization that has not saved its own configuration:

  • A card for each agent, with a switch that configures the agent, and the capabilities it is given, such as routing its model traffic through AgentPass or Block direct traffic
  • For every agent: what happens if AgentPass can't be reached, Let traffic through or Stop traffic, and how often desktops check for new settings, from 10 to 3,600 seconds

Click Save to publish the defaults. To return them to the built-in baseline, click Reset to defaults…, then Reset in Reset every agent to the default?. Discard drops changes you have not saved.

Maintain the Fleet Block-Host Lists​

The Fleet block-hosts (all tenants) card lists, for each tool that supports egress enforcement, the provider hostnames the tool is blocked from reaching directly when an organization enforces its egress. For example, api.anthropic.com for Claude Code, and api.openai.com and chatgpt.com for Codex. When a provider changes its endpoints, update the list here, then click Save fleet block-hosts.

Unlike the default configuration, the fleet block-host lists apply to every organization, including those that saved their own configuration. An organization adds its own hostnames on top of these lists. See Egress Enforcement.

How the Defaults Are Inherited​

Every organization inherits the platform defaults until it customizes its own settings:

  • An organization that has not saved its own configuration uses exactly what the default configuration specifies. An edit you make here reaches its desktops on their next check for new settings.
  • When an organization saves its own configuration, that configuration takes over for the organization. Reset to defaults… in the organization's Desktops → Desktop configuration → Configuration returns it to inheriting yours.
  • Every organization inherits the fleet block-host lists regardless, with its own extra hosts merged on top.