Skip to content

Settings

Settings is where shared platform behavior is configured. Unlike My Profile, this page affects the whole environment rather than just one user.

Some tabs are visible to all users, while others are admin-only.

The main Settings tabs

The current Settings page can include:

  • Parameters
  • AI Models
  • General Assistant
  • Channels & Bots
  • Integrations
  • Quotas
  • MCP Endpoint
  • Security
  • Observability

Non-admin users usually see fewer tabs. That is expected.

Parameters

Parameters is an admin area for platform identity and licensing.

It currently includes:

  • platform branding
  • platform logo
  • instance ID
  • license management

The instance ID is especially important during licensing and support work. The page can also show whether the active license comes from the environment or from a value stored in the platform.

AI Models

AI Models controls the model providers used by the platform.

This tab can include:

  • chat and reasoning providers
  • default reasoning effort
  • embedding model configuration
  • image model configuration
  • provider-specific model lists

If your environment manages providers outside the UI, XTM One shows that clearly and treats those values as locked.

General Assistant

General Assistant is an admin tab for the shared assistant used across the platform.

This is where admins can define:

  • the default prompt
  • the default model
  • the maximum number of reasoning steps
  • how long an agent may pause when it is waiting for work it delegated
  • which tools and resources the assistant can use
  • which agents it can hand work to
  • how it behaves across channels

Two of these deserve a word, because they bound different things:

  • Max Iterations limits how many tool-calling rounds an agent may take. It is about work done, not time spent.
  • Waiting sets two time limits for the wait tool — the longest single pause, and the total an agent may spend waiting in one run. An agent uses it when it has delegated a task and wants to re-check in a few minutes rather than poll for it continuously. A pause deliberately does not count against Max Iterations, which is why it needs its own limits; the run's own time budget still applies, and users can skip or cancel a wait at any time from the chat.

This tab affects the assistant experience seen by the whole organization unless a user overrides part of it in My Profile.

Channels & Bots

Channels & Bots is the shared routing and channel administration area.

It currently covers:

  • always-on web chat
  • external channel bot setup
  • receive and publish whitelists
  • bot-specific tools
  • anonymous access
  • private conversation handling
  • mention-only behavior in group channels

This is also where admins can review or edit the connection details for Slack, Teams, WhatsApp, Telegram, and other supported messaging platforms when those channels are enabled in the deployment.

For the setup of each platform, step by step, see Channels and bots.

Integrations

Integrations is an admin tab with its own sub-navigation.

It currently includes:

  • Catalog
  • OAuth Defaults

Use this tab when you want to manage which integration types are offered in the platform and what default OAuth behavior should apply when users configure them.

Quotas

Quotas is the platform-wide usage control area.

In XTM One, it is mainly about:

  • agentic execution quotas
  • license-driven limits
  • per-user or per-group quota overrides

Some other deployments also show extra quota types such as LLM proxy usage.

Use this tab when you need to understand whether the environment is operating under a shared license limit or a manually configured quota policy.

Agent Failure Pool

An agentic action is deducted from the user's action quota before the agent starts, so a run that fails has already spent an action on work nobody received. The Agent Failure Pool card is where that is accounted for: each agent's first few failures are credited back instead of deducted, and the card shows how much of that allowance each agent has spent, how many pools are exhausted (and therefore spending actions on failures again), and the date the allowance renews.

The allowance renews once a year, on your XTM license anniversary. Its size is set by the operator in the environment and is deliberately not editable here — it decides what is billable.

The card separates the two reasons an action comes back, because only one of them is rationed:

  • Agent failure — the run failed on its own merits. This spends one slot of that agent's allowance, and the per-agent table shows how many slots are left.
  • No LLM call — the run never reached a model: the provider was unreachable, down or not configured, or the platform abandoned the work itself (worker lost, deadline blown) — assignment runs and background sub-agent tasks alike. Credited back for free, outside the allowance, however often it happens: no LLM was called, and an incident on the platform's side must not ration what a user gets. The Provider column counts those per agent.

Some agents carry a Platform badge. Those are the seeded platform automations, whose scheduled runs never consume the action quota at all — so they can never appear here for that work. A row exists for one only because someone triggered it manually, which is charged like any other run.

One action is available: Enter a support code. Filigran support can issue a single-use code that gives every agent on the platform a full allowance again without waiting for the renewal date — after an incident on their side, for instance. Paste the code (XTMP-…) and it is verified on the spot, with no outbound call; a refusal explains itself (not issued by Filigran, expired, issued for another platform, already used). Codes already redeemed are listed underneath with the date and the administrator who used them.

MCP Endpoint

MCP Endpoint is the admin version of MCP exposure.

It lets administrators:

  • generate or revoke the global MCP key
  • copy the platform MCP endpoint
  • choose which agents are exposed globally
  • review the connection snippet for external clients

This is the shared endpoint, separate from the personal MCP exposure available in My Profile.

The page also contains the Platform MCP Servers card, which controls the native OpenCTI, OpenAEV, and OpenGRC MCP servers (/mcp/opencti, /mcp/openaev, /mcp/opengrc):

  • a global enable/disable toggle (on by default)
  • the endpoint URL and live connection status for each platform

These servers activate automatically when a platform is registered with XTM One and expose business and knowledge tools only. See Platform MCP servers for details.

A separate Platform Tools MCP Server card controls /mcp/xtm, which exposes XTM One's own tools — agent traces, agents, assignments, runs, knowledge bases, prompts, skills, custom tools, integrations, and variables — to external MCP clients:

  • a global enable/disable toggle, off by default
  • the endpoint URL, with a copy button

It is off by default because it exposes this instance's configuration surface rather than a connected platform's content. Each caller only reaches what they can already see and manage in the UI, and every write goes through the same permission gates as the REST API.

Once enabled, the card also offers downloadable installer packages (Claude Code, Claude Desktop, Agent Plugins) — the same ones users get in their profile, so you can review exactly what is handed out. With One-click install on, a download creates a new personal API key for the downloading user and writes it into the package; those key creations appear in the audit log like any other, and revoking a key cuts off only the client it was made for. See Platform tools MCP server for details.

Security

Security controls sign-in and identity behavior.

This tab can include:

  • local authentication rules
  • registration policy
  • OpenID Connect
  • SAML 2.0
  • SAML group mapping
  • allowed email domains
  • memory purge controls

This is usually handled only by platform administrators or identity administrators.

Observability

Observability covers tracing and diagnostics.

In the current UI, this mainly includes:

  • Langfuse configuration
  • tracing for chat
  • tracing for runs
  • tracing for API-level behavior where supported

Some deployments can expose more observability options than others.

What regular users should know

If you are not an administrator, you may only see AI Models and Channels & Bots, or even fewer options depending on deployment.

That does not mean your account is broken. It only means shared configuration is intentionally restricted.

Next step

The AI Catalog page explains where you can browse published resources and add them to your account.