Admin console

Edition: the admin console is an Enterprise Edition feature. The Developer Edition ships no admin console — it is a single-user local runtime.

The admin console is the operator's control panel for a StrataBI deployment: feature toggles, module visibility, role mapping, pinned dashboards, and archive management. It is gated by RBAC — only users whose role resolves to Admin can reach it — so in a deployment with RBAC enabled it is invisible to everyone else.

It is organized into tabs.

Settings

Deployment-wide feature switches and runtime settings:

Feature toggles — switches for favorites, AI, RBAC, and auto archive.

The AI and RBAC toggles are live gates that take effect immediately on the running instance. The favorites and auto archive switches are stored but not yet enforced by the runtime — favorites are currently always available, and auto archive is a no-op (see Archive & retention). See Favorites & pins and Roles & access control.

Auto archive after N days — a stored retention threshold (default 90); **not yet

enforced** — see Archive & retention.

AI / Bedrock — the model id and related settings the AI home page uses; see

AI generation (Bedrock).

Theme is not set here — it is a deploy-time value (STRATABI_THEME /

the Terraform theme variable). The Settings tab shows the current theme but changing it requires a redeploy, because a running task cannot re-serve a new stylesheet. See Theming.

Some controls are deployment-level and may still require a Terraform/environment change rather than a live toggle; the tab flags these where they apply.

Modules

A read-only view of the installed module registry — the modules discovered in your system bucket and registered in DynamoDB — plus selection of the default modules exposed to the AI generator. This mirrors what you install and register with StrataCTL; see Modules and Build a module.

RBAC

Maps your identity provider's groups/claims to StrataBI roles (Viewer, Builder, Admin) and toggles the finer permissions — notably Artifacts (downloads) and Raw HTML. Role changes re-evaluate immediately. This is the UI over the model described in Roles & access control; the identity layer that feeds it is in Authentication & SSO.

Pins

Curate the shared home page: Pin a dashboard to surface it above everyone's favorites and recents, or Unpin to remove it. This tab also holds the git-registry admin override — the only place a pinned dashboard can be deregistered from version control. See Favorites & pins and Dashboards as code.

Archive & retention

Dashboards live in your S3 system bucket, partitioned by save-month (analyst/dashboards/<YYYY_MM>/…; see Naming & payloads). How long they stay viewable is a retention question — and today it is governed by the S3 lifecycle policies on your own bucket, which you own and control, not by StrataBI. Expiring or transitioning old month partitions is precisely what limits how far back dashboards can be viewed, so set lifecycle rules to match your retention needs (and enable S3 versioning if you want a recovery backstop).

Note

Preview. The Archive tab (per-month archive / restore) and the auto archive after N days setting are scaffolded but not wired in the current runtime — the buttons return a placeholder and the setting is stored, not enforced. Use S3 lifecycle rules on the dashboard bucket for retention until in-app archiving ships. Favorites, Pins, RBAC, Modules, and the AI / theme settings are the working surfaces today.

Access

The console is reachable only when the caller's role resolves to Admin. Role comes from your identity provider's group/role claims via the mapping on the RBAC tab, so granting or revoking admin access is done in your directory and the RBAC mapping — there is no separate admin user list to maintain.