Admin Guide

The Admin Guide covers everything you configure and monitor from the Arbitex admin console at admin.arbitex.ai. It is UI-first: every page starts with what you see and click in the console, then gives the equivalent API call for teams that automate.

How this guide is organized

The guide mirrors the admin console’s sidebar five groups, 1:1 — so “where do I configure X in the guide” matches “where do I configure X in the console.” The first four groups are for configuration; Monitoring is for reading telemetry.

Users & AccessUsers, invites, groups & roles, authentication methods, MFA enforcement, and sessions.

Security & DLPPolicy packs, the 5-tier DLP pipeline, content detection, governance actions, and quarantine.

Models & RoutingProviders, model catalog and routing, quotas, cost governance, and the kill switch.

SystemConfiguration, API keys, OAuth clients, webhooks, BYOK, IP allowlist, and org configuration.

MonitoringUsage, latency, cost, alerts, health, audit log, and DLP trends — how to read the telemetry.

The per-page pattern

Every Admin Guide page follows the same shape so you always know where to look:

1. What it does — the capability in one or two sentences.
2. Configure in the UI — the console walkthrough, with a screenshot and numbered steps.
3. API equivalent — the curl/SDK call for the same change, for automation.
4. Plan & availability — which plan tier the feature requires. Features above your tier render visible but disabled in the console with an upgrade prompt.
5. Deployment notes — any differences on a Hybrid Outpost, including air-gapped behavior (for example, no telemetry rollup in an air-gapped deployment).

Getting to the console

Sign in at admin.arbitex.ai. The console opens on the Users panel by default. The left sidebar groups every panel under the five headings above; click a group heading to expand it, then a panel to open it. Your last-opened panel is remembered between visits.

Documentation data-source policy — synthetic data only

Every screenshot in this guide is captured against a non-production Arbitex demo instance populated with the fictional Citadel synthetic dataset — never a real customer tenant.

We never use client data in documentation. Customer tenants are confidential, so all documentation and marketing artifacts use synthetic Citadel data on a non-production demo instance only. Names, usage figures, and identifiers in these screenshots are fictional. See the screenshot pipeline for how captures are produced and guarded.

Screenshots currently marked “capture pending” are labelled placeholders; they are replaced with real captures from the demo instance as each surface is captured.

Start with the pilot

Users & Access is the fully worked pilot section — it demonstrates the complete per-page pattern end-to-end. The other four groups are scaffolded and fill in on the same template.

Begin: Users & Access →The most-trafficked onboarding surface — add your team, wire up SSO, and enforce MFA.