Dashboard, KAIA and accounts

Where you land, what the assistant found, and the guests, vouchers and profiles you manage.

Nearly every page below is permission-gated. If a colleague cannot see one, that is their role rather than a fault — Roles is where to look.

Dashboard

/admin/dashboard

The customizable widget dashboard you land on — live sessions, logins, bandwidth, and whatever else you've added.

When you would open it. First thing in the morning, or whenever you want a fast operational read without opening a report.

Before it has anything on it. At least one controller or zone sending accounting for the widgets to have anything to plot; a brand-new tenant gets an empty default dashboard until then.

Needs the view-dashboard permission.

KAIA

/admin/system/kaia

KAIA (Kiwire AI Assistance) — a heartbeat that runs 13 detectors every 15 minutes, narrates what it finds, and lets you apply a small catalog of pre-approved fixes.

When you would open it. To see what KAIA caught since the last heartbeat, ask it a question about this tenant, or apply or dismiss one of its suggestions.

Before it has anything on it. KAIA switched on for this tenant (the A.I Model card on System › Settings) and made available by the platform — otherwise this page renders an off-state instead of any data — plus an AI credential available (the tenant's own key, or the platform key) for it to actually run.

What it won't touch: the action catalog only covers small, named, permission-gated tweaks — a profile's limits, a zone's active/journey/forced-profile setting, a campaign's pause or resume — never admins, roles, secrets, credentials, payments, the licence, RADIUS, MFA or connectors, and it never deletes anything. There is no free-form action and no autopilot; every apply is a deliberate click.

Needs the view-kaia permission. Only when the kaia feature is enabled for the tenant.

→ KAIA

Account

Users

/admin/accounts/users

The list of guest and user accounts on this tenant — create, edit, reset, or drill into a single user's devices, login records, sessions and certificates.

When you would open it. Onboarding an account by hand, looking up one guest's history, or resetting a stuck session.

Before it has anything on it. At least one active profile (and, if you use zones, a zone) to offer when creating or editing a user — the create form's dropdowns only show what already exists.

Needs the view-users permission.

→ Account, voucher and top-up fields

Vouchers

/admin/accounts/vouchers

The list of vouchers issued on this tenant — generate a new batch, edit or reset an individual voucher, and see its devices, login records and sessions. A batch can carry a group name, visit date and number of people.

When you would open it. Generating vouchers for an event, a visiting group or a reseller batch, or tracking down what happened to one specific code a guest is asking about.

Before it has anything on it. At least one active profile to attach to the batch. Set a voucher prefix on the tenant first if you want generated codes to look like more than "VOU" plus today's date, which is the fallback.

Needs the view-vouchers permission.

→ Account, voucher and top-up fields

WiFi Certificate

/admin/accounts/wifi-certificates

The client certificates issued for cert-based (802.1X/EAP-TLS) WiFi login — view details or revoke one. Certificates aren't created from this page.

When you would open it. Troubleshooting a WiFi Enterprise device that won't authenticate, or revoking a certificate for a lost or decommissioned device.

Before it has anything on it. The certificate panel enabled on the WiFi Enterprise portal config — without it the page shows a warning instead of usable data — and at least one device that has gone through enterprise enrollment to actually have a certificate to list.

Needs the view-wifi-certificates permission.

Profiles

/admin/accounts/profiles

The bandwidth and access profiles — speed, quota, session time, idle timeout — that get attached to users, vouchers and topup codes.

When you would open it. Setting up a new plan tier, or adjusting limits tenant-wide by editing a profile that's already assigned to many accounts.

The shared dependency: this is the one Accounts page the others lean on. Users, vouchers and bulk-update all pull their profile dropdown from what already exists here, so an empty list on this page means empty dropdowns everywhere else in Accounts.

Needs the view-profiles permission.

Topup Code

/admin/accounts/topup-codes

Prepaid top-up codes — a batch of one-time codes, each carrying a data quota and/or extra time, that a guest redeems against their own account to extend it.

When you would open it. Generating a batch of codes to sell or hand out (for example, printed and sold at a counter), and tracking which ones are used, suspended or expired.

Before it has anything on it. A topup code prefix set on the tenant if you want generated codes to be recognizably yours — unlike vouchers, there is no automatic fallback prefix here.

Needs the view-topup-codes permission.

→ Account, voucher and top-up fields

Bulk Update

/admin/accounts/bulk-update

A bulk-edit tool over existing user and voucher accounts — filter by type, status or search, then apply a profile, zone or status change to every matching row at once.

When you would open it. Retiring a profile across everyone on it, moving a batch of vouchers to a different plan, or suspending a group of accounts together instead of one at a time.

Before it has anything on it. Accounts that already exist — it edits, it does not create — and at least one active profile or zone to reassign them to.

Needs the bulk-update-accounts permission.

---

This list is read from the admin menu itself, so it cannot fall behind it.