User Groups & Permissions Guide
Overview
GATE implements a role-based access control (RBAC) model that ensures secure and organized user management. Permissions are never assigned directly to individual users. Instead, users inherit their permissions from one or more groups, allowing you to tailor user experiences while maintaining platform security.
Every group provides access to a specific functional area (such as AAA, payments, or advertising) at a defined privilege level (full admin, read-only admin, or reports-only). You can assign multiple groups to a single user to grant cross-functional responsibilities.
flowchart LR
U[User] -->|member of| G1[Group A<br/>e.g. AAA admins]
U -->|member of| G2[Group B<br/>e.g. Payment reports]
G1 -->|grants| P1[Permissions on AAA]
G2 -->|grants| P2[Permissions on Payment reports]
P1 --> UI[GATE admin UI]
P2 --> UI
β Key Concept: Groups are additive. A user belonging to multiple groups receives the union of all their permissions. This allows you to compose roles rather than creating new groups for every possible combination.
Permission Levels
Most functional areas provide three standard permission levels. Always select the lowest level that enables users to complete their tasks effectively β this follows the principle of least privilege.
Standard Permission Levels
| Level | Indicator | Access Granted | Typical Use Cases |
|---|---|---|---|
| Admin | π’ | Full CRUD operations (create, view, update, delete) on area resources | Day-to-day feature configuration and management |
| Read-only Admin | π‘ | Browse all objects in the area without modification or deletion capabilities | Auditors, trainees, support staff conducting investigations |
| Reports | π΅ | Access to dashboards, charts, and transaction listings without configuration access | Business analysts, finance teams, marketing personnel |
Special Cross-Cutting Roles
Beyond the standard levels, GATE includes two important cross-cutting roles:
| Role | Indicator | Access Granted |
|---|---|---|
| End User | β« | Personal profile access, password changes, and preference settings (non-administrative) |
| Expert Mode | π£ | Unlocks hidden "Expert Mode" toggle revealing advanced menus and destructive operations (bulk deletes, internal settings) |
β οΈ Expert Mode Warning: Only grant Expert Mode access to senior operators who understand the consequences of destructive operations.
Functional Areas
GATE organizes functionality into distinct areas, each with its own group hierarchy using the three standard permission levels where applicable.
| Area | Scope |
|---|---|
| π Global Administration | Cross-cutting operations, organization-wide configuration, and platform health monitoring |
| π‘ AAA | Authentication, Authorization, and Accounting β profiles, realms, clients, home servers, session logs |
| π Account | Tenant/account configuration including plans, services, lists, parameters, and site settings |
| π£ Advertisement | Campaign management, banner configuration, segmentation rules, and advertising transaction logs |
| π API Logs | Platform API request history inspection for debugging and auditing purposes |
| π± Devices & Applications | Mobile/desktop app registrations, device metadata, connection logs, and app subscriptions |
| π‘ Hotspot Monitoring | Real-time access point health monitoring including reachability, uptime, coverage, and availability reports |
| π³ Payments | Payment plan management, gateway configuration, transaction processing, and refund handling |
| π₯ Users | End-user account management, social login configuration, and user-level activity logs |
| π Reports & Dashboards | Cross-area analytics, KPI tracking, and exportable report generation |
| π SONDA / User Experience | Real-world user experience monitoring including latency, throughput, and client-side reachability measurements |
Group Catalog
The following tables detail every built-in group shipped with GATE, organized by functional area. Group names are stable identifiers that you can search for in the group administration interface.
Global Administration
| Group | Level | Description |
|---|---|---|
GATE admins |
π’ Admin | Comprehensive platform administration access for day-to-day operations across most areas |
GATE read-only admins |
π‘ Read-only | Platform-wide browsing access without modification capabilities |
GATE reports |
π΅ Reports | Access to dashboards, KPIs, and transaction listings across the platform |
π‘ Usage Recommendation: These general-purpose roles serve as excellent starting points for most operators. Combine them with area-specific groups when users require deeper access to particular modules.
AAA (Authentication, Authorization, Accounting)
| Group | Level | Description |
|---|---|---|
GATE AAA admins |
π’ Admin | Complete AAA administration including profiles, realms, clients, home servers, and accounting |
GATE AAA admins w/o Portals |
π’ Admin | Full AAA administration excluding captive portal builder access |
GATE AAA admins w/o Portals RO |
π‘ Read-only | Read-only AAA administration without captive portal builder access |
GATE AAA read-only admins |
π‘ Read-only | Read-only access to the complete AAA functional area |
GATE AAA reports |
π΅ Reports | AAA accounting reports, session analytics, and traffic dashboard access |
GATE AAA user admins |
π’ Admin | Specialized role for managing AAA end-users only (profiles, attributes, credentials) without infrastructure access |
π― Selection Guidelines:
- Use
AAA adminsfor complete AAA stack ownership- Use
AAA admins w/o Portalswhen captive portal design is managed separately- Use
AAA user adminsfor support desk personnel who only reset credentials or adjust user attributes- Use
AAA reportsfor analytics roles that must not access configuration
Account Management
| Group | Level | Description |
|---|---|---|
GATE account admins |
π’ Admin | Complete account administration including plans, services, lists, parameters, and site settings |
GATE account read-only admins |
π‘ Read-only | Read-only account administration access for audit and review purposes |
π― Selection Guidelines:
account adminsrepresents the closest equivalent to a tenant "owner" role β grant sparingly.account read-only adminsis ideal for auditors and onboarding verification.
Advertisement Management
| Group | Level | Description |
|---|---|---|
GATE advertisement admins |
π’ Admin | Complete advertisement administration including campaigns, banners, and segmentation rules |
GATE advertisement read-only admins |
π‘ Read-only | Read-only advertisement administration for audit purposes |
GATE advertisement reports |
π΅ Reports | Advertisement reporting and transaction access including impressions, clicks, and conversions |
π‘ Team Separation: Assign
advertisement adminsto marketing teams,advertisement reportsto analytics teams, andadvertisement read-only adminsto finance auditors.
API Logs
| Group | Level | Description |
|---|---|---|
GATE API Logs read-only |
π‘ Read-only | API request log browser access for debugging and auditing |
π‘ Usage Recommendation: Ideal for integration teams and third-party partners who need API call troubleshooting capabilities without broader platform access.
Devices & Applications
| Group | Level | Description |
|---|---|---|
GATE device admins |
π’ Admin | Device and application administration including registrations, subscriptions, and configuration |
π‘ Usage Recommendation: Designed for mobile/desktop application operations teams responsible for registered device lifecycle management.
Hotspot Monitoring
| Group | Level | Description |
|---|---|---|
GATE hotspots monitoring |
π’ Admin | Hotspot monitoring administration including monitoring profiles, thresholds, and alert configuration |
GATE hotspots monitoring read-only |
π‘ Read-only | Read-only access to hotspot monitoring dashboards and availability reports |
π‘ Usage Recommendation: Essential for network operations center (NOC) teams monitoring access point health and coverage.
Payment Management
| Group | Level | Description |
|---|---|---|
GATE payment admins |
π’ Admin | Complete payments and plans administration including pricing, gateways, and plan lifecycle |
GATE payment read-only admins |
π‘ Read-only | Read-only payment area access for audit and compliance |
GATE payment reports |
π΅ Reports | Payment reporting and transaction access including revenue dashboards and reconciliation exports |
π― Selection Guidelines: Finance teams typically need
payment reportsfor reconciliation pluspayment read-only adminsfor transaction investigation. Reservepayment adminsfor billing operations personnel only.
User Management
| Group | Level | Description |
|---|---|---|
GATE users admins |
π’ Admin | User account and user log administration |
GATE users RO |
π‘ Read-only | Read-only access to user lists and user activity logs |
Users |
β« End user | Standard end-user role providing profile access and password change capabilities |
Users: Expert mode |
π£ Expert | Enables Expert Mode toggle in admin UI, unlocking advanced menus and destructive operations |
β οΈ Expert Mode Security Notice: Expert Mode reveals advanced and destructive operation menus (bulk accounting record deletion, low-level configuration, internal tooling). Grant
Users: Expert modeexclusively to trained senior operators who understand operational consequences.
Reports & Dashboards
| Group | Level | Description |
|---|---|---|
Report admins |
π’ Admin | Report and dashboard administration including creation, editing, and sharing of custom reports |
π‘ Usage Recommendation: Designed for business intelligence teams responsible for building and maintaining organizational dashboards.
SONDA / User Experience
| Group | Level | Description |
|---|---|---|
SONDA admins |
π’ Admin | SONDA probing and user experience measurement system administration |
SONDA reports |
π΅ Reports | SONDA reporting and transaction access including latency, throughput, and reachability metrics |
π‘ Usage Recommendation: Essential for quality-of-experience (QoE) teams monitoring real user service perception.
Access Matrix
This visual summary shows available group combinations for each functional area and permission level. Empty cells indicate no pre-built group exists for that combination β use the closest available level or combine multiple groups.
| Area | π’ Admin | π‘ Read-only | π΅ Reports | Notes |
|---|---|---|---|---|
| Global | GATE admins |
GATE read-only admins |
GATE reports |
Starting point for most operators |
| AAA | GATE AAA admins |
GATE AAA read-only admins |
GATE AAA reports |
w/o Portals variants available |
| AAA (user-level) | GATE AAA user admins |
β | β | Support/helpdesk focused |
| Account | GATE account admins |
GATE account read-only admins |
β | Tenant configuration |
| Advertisement | GATE advertisement admins |
GATE advertisement read-only admins |
GATE advertisement reports |
Complete coverage |
| API logs | β | GATE API Logs read-only |
β | Integration/debug role |
| Devices & apps | GATE device admins |
β | β | Limited coverage |
| Hotspot monitoring | GATE hotspots monitoring |
GATE hotspots monitoring read-only |
β | NOC teams |
| Payments | GATE payment admins |
GATE payment read-only admins |
GATE payment reports |
Complete coverage |
| Users | GATE users admins |
GATE users RO |
β | See also Users and Users: Expert mode |
| Reports & dashboards | Report admins |
β | β | BI team role |
| SONDA / UX | SONDA admins |
β | SONDA reports |
QoE role |
Common User Profiles
These ready-to-apply group combinations cover most real-world operational requirements.
π§βπΌ Platform Operator (Day-to-Day Admin)
Group Assignment:
GATE adminsGATE AAA adminsGATE account adminsGATE device admins
Role Description: Handles platform configuration, service onboarding, and operational issue resolution across all areas. Expert Mode is not included by default.
π Helpdesk / Tier-1 Support
Group Assignment:
GATE read-only adminsGATE AAA user adminsGATE users ROGATE API Logs read-only
Role Description: Platform browsing, user credential resets, and API log inspection without configuration modification or data deletion capabilities.
π Business Analyst / BI
Group Assignment:
GATE reportsGATE AAA reportsGATE advertisement reportsGATE payment reportsSONDA reportsReport admins(optional, for dashboard creation)
Role Description: Dashboard-focused access without configuration capabilities, eliminating accidental change risks.
π° Finance / Billing
Group Assignment:
GATE payment read-only adminsGATE payment reportsGATE read-only admins(optional, for context)
Role Description: Transaction reconciliation and payment configuration auditing without modification capabilities.
π£ Marketing Operator
Group Assignment:
GATE advertisement adminsGATE advertisement reports
Role Description: Campaign creation and measurement with isolated functional scope.
π Network Operations (NOC)
Group Assignment:
GATE hotspots monitoringGATE AAA reportsSONDA reports
Role Description: Real-time access point health monitoring with session analytics and user experience correlation capabilities.
π Senior Operator (with Destructive Tooling)
Group Assignment:
GATE adminsGATE AAA adminsUsers: Expert mode
Role Description: Standard operator capabilities enhanced with Expert Mode access. Reserve for trusted operators exclusively.
π€ End User (Self-Service)
Group Assignment:
Users
Role Description: Personal profile and password management without administrative area access.
Best Practices
π‘ Principle of Least Privilege
Always assign the minimum permission level required for job function completion. Prefer read-only admins over admins for investigation or audit roles. Choose reports over read-only admins when users only need dashboard access.
π Compose Rather Than Customize
Resist creating specialized groups for individual users. Combining two or three built-in groups typically addresses requirements while maintaining audit simplicity.
π§ͺ Test in Staging Environment
Before production deployment, apply new user profiles (group combinations) to test users in non-production environments. Verify exact menu, button, and action visibility before real user rollout.
π Periodic Review Schedule
Implement quarterly group membership reviews. Revoke admins and Expert Mode capabilities from users who no longer require them. Former employee accounts with lingering admin access represent the most common security incident cause.
π¨ Separation of Duties
When possible, distribute configuration and audit responsibilities among different personnel:
- Payment configuration (
payment admins) and payment auditing (payment read-only admins+payment reports) should involve different individuals - Campaign creation (
advertisement admins) and advertising budget approval (viapayment reports) should involve different individuals
π Expert Mode Access Control
Treat Users: Expert mode as break-glass permission due to irreversible operation access:
- Grant exclusively to named senior operators
- Document justification for each recipient
- Implement quarterly Expert Mode group membership reviews
- Remove temporary Expert Mode access immediately upon task completion
Frequently Asked Questions
Can I modify built-in groups to add or remove permissions?
While technically possible, modification is not recommended. Built-in groups may receive updates in future GATE releases, overwriting manual changes. Instead, create additional groups with required deltas and assign both to users.
Can a user belong to multiple groups simultaneously?
Yes. Group memberships are additive β users inherit the union of all permissions from assigned groups. This represents the recommended approach for role composition.
Which groups should new support agents receive?
Start with GATE read-only admins + GATE users RO + GATE API Logs read-only. Add area-specific groups as responsibilities expand.
A user sees unauthorized menus. How do I remove access?
Remove the group granting menu access. If the menu persists, verify the user is not a superuser β superusers bypass the group system entirely and see all menus. Downgrade to regular user status and assign appropriate groups instead.
How do I identify which group grants specific menu access?
Each admin section corresponds to a functional area (AAA, payments, advertising, etc.). Match the menu to the area using Section 3: Functional Areas, then select the appropriate level from Section 5: Access Matrix.
Can I grant access to organization subsets only?
Yes β group-granted permissions are automatically scoped to the user's organization and its sub-organizations. A user with GATE admins in organization "Acme" will only see and administer Acme and its children, never sibling organizations.
π¬ Documentation Feedback: If you believe a group is missing, misnamed, or if use cases in this guide don't match your requirements, please submit a documentation request for review in the next release.
No comments to display
No comments to display