Skip to content
Documentation

Settings

Settings is the unified administration console.

Settings is the unified administration console. Its top tabs are General, Identity & Access, Integrations, Policy and System; the left rail selects a section. Deep links use ?tab=<topTab>&section=<section>.

Settings in light mode Settings in dark mode

The screenshot records the canonical /settings page once. The sections below are query-string views of that same page, so the guide does not duplicate near-identical screenshots for each rail entry.


Change your own account details and password preferences. A forced password change restricts the session to the change-password flow, and a successful change revokes existing sessions.

Tenant display name, locale/time-related defaults, operator-facing defaults and other non-security configuration.

SuperAdmin-only product branding: logo, colours and login appearance. Branding changes should be reviewed in both light and dark themes.


Create local users, assign roles, manage status and configure group visibility where device-group scoping is enabled.

Users & Roles in light mode Users & Roles in dark mode

Configure Entra ID/OIDC provider settings, claims and sign-in behavior. Keep a working break-glass local administrator until SSO has been proven through login, MFA and logout.

Restrict sign-in by network, device or other tenant policy conditions. Test with a second session so an administrator does not lock out the entire tenant.


Forward endpoint/alert data to Cortex XSIAM. Test connectivity before enabling a broad forwarding path.

Map devices/groups into Freshservice configuration items for ownership and ticket context.

Store the upstream AMTD tenant GUID and connection settings. The value is required when AMTD is enabled; the proxy injects it on every outbound call so an individual page cannot hardcode a tenant.

Enable or disable capability modules such as Threat Detection, UEBA, Sandbox, vulnerability feed and other tenant features. A disabled module shows an explicit disabled state, not a generic loading error.

Apple MDM credentials and configuration used by native macOS security workflows.

Sender, relay, authentication and delivery-test settings used by scheduled reports and notifications.

Outbound webhook endpoints and event selection. Secret material is write-only; test with a non-destructive event before enabling production delivery.

Create scoped, expiring tokens for automation. Record token purpose and owner; revoke unused tokens on a schedule.

Enable and constrain an MCP server surface for approved AI/automation clients. Scope operations deliberately; this setting decides what an AI agent may request.

SuperAdmin-only event-bus/broker settings and test controls.

Provider settings for indicator lookup and feeds.

Sandbox provider key/token, defaults, privacy and quota settings. The product-facing page remains Sandbox; the vendor name appears here.

Threat Lens vulnerability-feed credentials used to enrich software inventory with CVE data.

Route selected alert types to external SIEM/SOAR/notification systems.


Reserved integration surface; currently marked Soon and blocked rather than exposing unusable sync actions.

Tenant-level policy behavior overrides. Keep changes rare and time-limited; each override should have an owner and reason.

Control automatic policy or trust actions derived from inventory classification. Avoid broad auto-allow rules until publisher quality has been reviewed.


Event and alert retention periods. Shorter retention reduces storage but destroys historical investigation scope; document the requirement before changing it.

Operational runtime values for background jobs and services. This is not a general “make the product faster” form; each value affects throughput, latency or reliability.

Tenant/group alert thresholds, including agent-offline timing and noise controls. In v7.3.1 tenants without a custom agent-offline threshold alert after 15 minutes rather than 24 hours.

Automatically recover from device signing-key desync. Understand the recovery path before enabling it fleet-wide.

Password policy, session controls and other tenant security settings.

SuperAdmin diagnostic surface for support and troubleshooting.

Pod/container/volume/node health for the deployed platform. This moved from About to System because it is an operational surface, not product identity.


  1. Know the setting’s blast radius.
  2. Use the lowest-duration change that proves the outcome.
  3. Keep one authenticated SuperAdmin session independent of SSO/conditional access.
  4. Test integrations before enabling forwarding.
  5. Screenshot or export the previous value when there is no built-in diff.
  6. Check Audit Log after saving.
  7. Verify the user-visible effect, not only the save toast.