Tenants and administrator roles
Airgate is multi-tenant: one Airgate platform hosts many customer organisations, each in its own tenant. Administrators work inside a tenant, with a role that limits what they can do. This page explains tenants, how requests are tied to them, and the administrator roles and permissions.
Tenants
Section titled “Tenants”A tenant is one customer organisation. Everything you configure belongs to exactly one tenant and is invisible to the others:
- network devices, device groups and site connectors;
- directories, local users, guest accounts and devices;
- access policies, enforcement profiles and MAC lists;
- the tenant’s Onboard CA and NAD CA, issued certificates and trusted CAs;
- integrations, webhooks, log export, settings;
- the Sign-in log, sessions, events and the audit log.
Each tenant has a display name, a short slug used in public addresses (for example the SCEP URL /scep/<slug>, guest portals /portal/<slug>/<portal> and BYOD portals /byod/<slug>/<portal>), and an ID. A new tenant is seeded with its defaults: built-in directories, enforcement profiles, authentication methods, disabled sample policies and its certificate authorities.
On an Airgate appliance, the organisation name you enter at first boot becomes the first tenant.
How a request finds its tenant
Section titled “How a request finds its tenant”| Request | Tenant from |
|---|---|
| RADIUS over UDP | The source address: the network device entry (address or subnet) that matches it. Network device prefixes of different tenants may not overlap. |
| RadSec | The client certificate of the connection. |
| Through a site connector | The connector, which belongs to one tenant, and then the original device address within that tenant. |
| TACACS+ | The source address of the network device. |
| Console and API | The administrator’s own tenant, or the tenant a platform administrator chose. |
| Portals, SCEP | The tenant slug in the address. |
Because the address of a UDP RADIUS request identifies the tenant, two tenants behind the same NAT address cannot both send UDP RADIUS directly. They must use RadSec or a site connector.
Administrators
Section titled “Administrators”Administrators sign in to the console with an e-mail address and password, or with single sign-on (Settings › Single sign-on: Microsoft Entra ID, Okta, Google or any SAML 2.0 or OpenID Connect provider). Settings › Administrators lists them. API keys (Settings › API keys) are OAuth2 client credentials with a role, for scripts and integrations.
| Role | Label in the console | For |
|---|---|---|
tenant_admin |
Tenant Administrator | Full control of the tenant, including administrators, API keys and settings. |
network_admin |
Network Administrator | Policy, identity, guest, onboarding and monitoring with CoA. Administration is view-only. |
helpdesk |
Help Desk | Troubleshooting: manage users, endpoints and guests, view policy and monitoring, send CoA. |
guest_operator |
Guest Operator | Receptionists and sponsors: create guest accounts and approve self-registrations. |
read_only |
Read-only Administrator | View the tenant’s screens, change nothing. |
platform_admin |
Platform Administrator | Cross-tenant operator: manages tenants and every tenant’s configuration, and the appliance (software update, backups). |
Permissions
Section titled “Permissions”| Permission | Allows | Tenant Admin | Network Admin | Help Desk | Guest Operator | Read-only |
|---|---|---|---|---|---|---|
policy:read |
View access policies, enforcement profiles, directories, network devices, sites | Yes | Yes | Yes | Yes | |
policy:write |
Change them; check a password in Test access | Yes | Yes | |||
identity:read |
View local users, devices, MAC lists | Yes | Yes | Yes | Yes | |
identity:write |
Change them | Yes | Yes | Yes | ||
guest:read |
View guest accounts, portals, Wi-Fi passes | Yes | Yes | Yes | Yes | Yes |
guest:write |
Create and change them | Yes | Yes | Yes | Yes | |
onboard:read |
View certificate authorities, certificates, BYOD | Yes | Yes | Yes | Yes | |
onboard:write |
Issue and revoke certificates, manage CAs and BYOD portals | Yes | Yes | |||
monitor:read |
Sign-in log, sessions, events, reports, logs | Yes | Yes | Yes | Yes | |
monitor:coa |
Send CoA, disconnect or bounce from the console | Yes | Yes | Yes | ||
admin:read |
View administrators, API keys, webhooks, log export, settings, integrations, server certificates | Yes | Yes | Yes | ||
admin:write |
Change them | Yes | ||||
platform:admin |
Manage tenants, software updates and backups | Platform Administrator only |
An administrator can only give others a role whose permissions they hold themselves, and never Platform Administrator inside a tenant. Platform administrators can reach every tenant; everyone else reaches only their own.
Every administrative change is recorded in Settings › Audit log with who made it, when and from where. Secrets are never written to it.