Day-to-day workflows
What admins actually do once a tenant is live. Four areas, each organized around the question "I want to ___; how do I do it?" No tour of the App's buttons — those are documented in the App itself. These pages describe the work.
Tune caching
Write rules. Express invalidation. Handle the warnings the rules analyzer raises before they bite.
Watch traffic
Read the dashboard, drill into a single statement, and stand up your own reports against the analytics API.
Share access
Invite teammates to a tenant. Revoke access cleanly when someone moves on.
Automate
Mint a personal access token, scope it down, and exchange it for a short-lived JWT for non-interactive work.
Pick by task, not by page
The App groups admin work by surface — rules, traffic, team, API explorer. These docs group it by intent. If you're trying to figure out which page of the App to open, every workflow page names the surface and links straight to it; if you're already in the App and want a deeper concept, every App page links back to the matching workflow doc.
If you haven't set up a tenant yet
Workflows start after the first cache hit. If you don't have a tenant yet, walk the first-hour get-started path — six steps from sign-up to seeing a hit in the App dashboard — and come back to these pages once traffic is flowing.
Ready to tune?
The first place most admins land. Cache rules are where Airbrx earns its keep — fine-grained on both halves.
Start with tune caching