Prerequisites
Before you change settings, confirm that:- You have permission to manage RADIUS settings.
- Your team agrees on the vocabulary you want operators to see.
- You know which metadata keys should be used consistently.
- You have the external URL patterns needed for shortcuts.
Labels
Open Settings in the RADIUS app to customize labels for:- Users.
- Folders or containers.
- Devices.
- Groups.
The default UI label for containers is shown as folders in the app. The underlying behavior is the same: folders organize users and nested folders.
Metadata
Metadata is custom key-value data on RADIUS objects. You can add metadata to:- Users.
- Groups.
- Realms.
- NAS devices.
display_nameis treated as the friendly user display name.site_iduses the Altostrat site picker when the UI can resolve sites.- Empty keys or empty values are not saved.
Metadata Shortcuts
Metadata shortcuts create external links from metadata values. They are useful when operators need to jump from a RADIUS record to a CRM, billing platform, support case, monitoring page, or internal admin system. A shortcut includes:- Parent type, such as user, group, realm, or NAS.
- Metadata key.
- Label.
- URL template.
- Optional icon.
<value> as the placeholder for the metadata value. For example, a customer_id metadata field can link to an external customer profile by inserting the customer ID into the URL.
Create A Shortcut From Metadata
Manage Shortcuts Globally
Open Settings to review all configured metadata shortcuts. The settings page groups shortcuts by parent type and metadata key. From there you can edit labels and URL templates or delete shortcuts that are no longer needed. Shortcut changes apply globally across matching objects.Recommended Metadata Keys
Use stable, predictable keys so shortcuts and filters remain useful over time:customer_idsite_idticket_idbilling_account_idexternal_idsupport_urlowner_team
Label And Metadata Governance
For larger RADIUS workspaces:- Decide labels before broad onboarding.
- Keep metadata keys lowercase and consistent.
- Use one key for one meaning.
- Prefer IDs over names when linking to external systems.
- Add shortcuts for common operator jumps.
- Review global shortcuts when renaming metadata keys.