Access
The Access tab holds the pages that decide who may connect and what the network device is told when they do. Network administrators use it to write access policies, connect directories, keep local accounts and try a sign-in before it happens for real.
Pages in this section
Section titled “Pages in this section”| Page | Console path | What you do there |
|---|---|---|
| Access policies | Access › Access policies | Group rules by who connects (employees, IoT, guests), choose the sign-in methods and directories per policy, and set what each rule sends: VLAN, role, SGT, ACL or an enforcement profile. Also holds the TACACS+ rules for switch and router logins. |
| Enforcement profiles | Access › Enforcement profiles | Build reusable sets of RADIUS reply attributes from vendor templates, for a rule to send. |
| Directories | Access › Directories | Connect Active Directory, LDAP, Microsoft Entra ID, Google Workspace, Okta, SQL, REST and RADIUS servers, test them and look up users. |
| Local users | Access › Local users | Create, import and manage accounts stored in Airgate itself. |
| Test access | Access › Test access | Run a pretend sign-in for a person or a MAC address and see which rule would match. |
Permissions
Section titled “Permissions”Every page in this section needs policy:read to open, except Local users, which needs identity:read. Changes need policy:write (Local users: identity:write). See each page for the roles that hold these permissions.
Related
Section titled “Related”© 2026 Airowire Networks Pvt. Ltd. Airgate is a product of Airowire.Product · Release notes · Security