Administration

The Admin module (/admin) is restricted to Admin-tier accounts in typical deployments. It surfaces directory, access control, and high-level reference counts for operations.

Scope of this guide

This page covers users, RBAC, and system / connectivity status. Day-to-day instrument reference browsing is documented under Reference data browser. Data freshness indicators for marks and WebSocket health are covered under Dashboard and Cash.

Summary cards

The top row shows live counts for Entities, Books, Accounts, Desks (all entities), Users, and Role defs — quick sanity checks for org coverage.

Users tab

The Users grid lists accounts from the auth admin API (/api/v1/auth/admin/users). Columns are inferred from the payload (IDs, tiers, metadata). Use it to review who can sign in and cross-check against RBAC assignments.

RBAC tab

RBAC has two sub-views:

Sub-view	Data
Assignments	GET /api/v1/admin/rbac/assignments — who has which roles/scopes.
Role definitions	Role rows from useRbacRoles — the catalog of definable roles.

An inline hint documents the endpoints used for assignments vs users.

Organization reference grids

Additional tabs (Entities, Books, Accounts, Desks) expose read-oriented grids for organizational structure (inferred columns). They are not a substitute for the Ref Data instrument browser; they exist to help admins reason about books and entities when tying access policies to the org chart.

System status (connectivity)

Atlas does not currently ship a dedicated per-service heartbeat page inside this module. Live connectivity is represented globally in the shell status bar (WebSocket state: WS: connected | connecting | …, last sequence / timestamp, and error text). If WebSocket status is not connected, streaming features (positions, cash feeds, invalidation-driven refetches) may be stale until the client reconnects.

---

For authentication and administrative APIs, see Authentication and the Interactive REST reference.