Platform Desktop Tools
Overview
On Platform Desktop Tools, a platform administrator sets the fleet-wide defaults for managed desktop tools 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 the moment it turns managed mode on, without configuring anything first.
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 per-organization settings a tenant administrator edits in the Desktop Tools view.
Open Platform Desktop Tools
Open Platform Desktop Tools from the navigation. It appears with the other platform pages, such as Tenants and Platform Observability, 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 managed mode switch and without inference routing. 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:
- Managed tools: which tools are selected by default, with each tool's capability tags
- Egress enforcement: which tools have direct traffic blocked by default, and any extra hosts to block on top of the fleet lists
- Behaviour: the default outage behavior, Fail open or Fail closed, and the default poll interval, from 10 to 3,600 seconds
Click Save to publish the defaults, or Reset to default to return them to the built-in baseline.
Reset to default takes effect as soon as you click it, with no confirmation step.
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 workstations on their next check-in.
- When an organization saves its own configuration, that configuration takes over for the organization. Reset to default in the organization's Desktop Tools view returns it to inheriting yours.
- Every organization inherits the fleet block-host lists regardless, with its own extra hosts merged on top.
Related
- Enabling Managed Desktop Tools — the per-organization settings that override these defaults
- Egress Enforcement — how an organization extends the fleet block-host lists
- Platform Observability — the equivalent fleet-wide default for Agent Observability