How do I allow Joxo where admins manage the agents?

On Claude Team and Enterprise, an admin turns on channels and allows the Joxo plugin. On Codex, an admin who keeps an MCP allowlist adds Joxo to it. People then set up Joxo as usual.

Claude Code: channels and the Joxo plugin#

Channels are off on claude.ai Team and Enterprise until an Owner turns them on, in Organization settings > Claude Code > Channels or in managed settings. To allow the Joxo plugin too:

{
  "channelsEnabled": true,
  "allowedChannelPlugins": [
    { "marketplace": "joxo", "plugin": "joxo" }
  ]
}

allowedChannelPlugins replaces Anthropic’s own list, so keep any other plugins your team uses in it. Save the file as managed-settings.json:

• macOS: /Library/Application Support/ClaudeCode/managed-settings.json
• Linux and WSL: /etc/claude-code/managed-settings.json
• Windows: C:\Program Files\ClaudeCode\managed-settings.json

/status in Claude Code shows whether the policy applies. Pro and Max accounts without an organization skip these checks. More in Anthropic’s managed settings and channels guides.

Claude Code: an MCP allowlist#

If you set allowedMcpServers, include Joxo’s server:

{ "allowedMcpServers": [{ "serverName": "joxo" }] }

See Anthropic’s managed MCP guide.

Codex: an MCP allowlist#

With an mcp_servers allowlist in requirements.toml, Codex starts a server only when its name and identity both match. Joxo’s server is named joxo and runs on Node.js; use the full path of the Node.js that runs joxo on your machines:

[mcp_servers.joxo]
identity = { command = "/usr/local/bin/node" }

See OpenAI’s managed configuration guide.

Related#

• Sign-in, SCIM and audit
• Security, privacy and terms