Groups
Groups let you apply shared settings to multiple users at once. Instead of configuring bandwidth limits, session timeouts, or VLAN assignments for each user individually, you create a group with these settings and add users to it.
Creating Groups
- Navigate to Users > Groups
- Click Add Group
- Enter a group name and description
- Configure group attributes
- Click Save
Group Properties
| Field | Description |
|---|---|
| Name | Unique identifier for the group |
| Description | Optional description of the group's purpose |
| Priority | Default priority when users are added |
Group Attributes
Groups can have both check and reply attributes that members inherit.
Common Use Cases
Bandwidth Limiting
Reply Attribute: WISPr-Bandwidth-Max-Down := 5000000
Reply Attribute: WISPr-Bandwidth-Max-Up := 2000000
Session Time Limits
Reply Attribute: Session-Timeout := 3600
Reply Attribute: Idle-Timeout := 600
Concurrent Session Limits
Check Attribute: Simultaneous-Use := 2
VLAN Assignment
Reply Attribute: Tunnel-Type := VLAN
Reply Attribute: Tunnel-Medium-Type := IEEE-802
Reply Attribute: Tunnel-Private-Group-Id := 100
Group Membership
Adding Users to Groups
- Navigate to the user's profile
- Click Add to Group
- Select the group
- Set the priority (1-10, where 1 is highest)
- Click Save
Priority Evaluation
When a user belongs to multiple groups:
- Groups are evaluated in priority order (1 first, then 2, etc.)
- Check attributes are matched against the authentication request
- When all check attributes of a group match, reply attributes are returned
- Evaluation stops at the first matching group
Example
A user belongs to:
- Premium Users (Priority 1) - High bandwidth
- Staff (Priority 2) - Standard bandwidth
If Premium Users' check attributes match, the user gets high bandwidth settings and Staff group is not evaluated.
Organizational Units
Organizational Units (OUs) provide an alternative way to organize users hierarchically.
Key Differences
| Feature | Groups | Organizational Units |
|---|---|---|
| Membership | Multiple per user | One per user |
| Hierarchy | Flat | Hierarchical |
| Attribute inheritance | Via priority | From parent OU |
Best Practices
- Use descriptive names - Make group purposes clear
- Document policies - Use descriptions to explain group settings
- Test thoroughly - Verify attribute inheritance works as expected
- Review regularly - Remove unused groups and update policies as needed
- Consider priority carefully - Plan the evaluation order for overlapping groups