> ## Documentation Index
> Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Settings, Labels, Metadata, and Shortcuts

> Customize RADIUS labels, use metadata fields, and create global metadata shortcuts to external systems from the Radius UI.

RADIUS settings let you tune the UI language and connect RADIUS records to external systems. The settings area covers label customization and metadata shortcuts, while individual users, groups, realms, and NAS devices each expose metadata fields on their detail pages.

## 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.

Each label has singular and plural forms. The UI uses these labels throughout the RADIUS workspace, including navigation, list headers, empty states, buttons, and detail pages.

Use label customization when your organization has established terms such as customers, subscribers, tenants, locations, clients, devices, or policies.

<Note>
  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.
</Note>

## Metadata

Metadata is custom key-value data on RADIUS objects. You can add metadata to:

* Users.
* Groups.
* Realms.
* NAS devices.

Metadata appears in the detail sidebar for each object. It can be edited, copied, and used as the basis for shortcuts.

Special metadata behavior:

* `display_name` is treated as the friendly user display name.
* `site_id` uses 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.

The URL template uses `<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

<Steps>
  <Step title="Open an entity detail page">
    Open a user, group, realm, or NAS device that has metadata.
  </Step>

  <Step title="Find the metadata field">
    In the metadata sidebar, hover or open the shortcuts control for the field.
  </Step>

  <Step title="Add a shortcut">
    Enter a label and a URL template that includes `<value>`.
  </Step>

  <Step title="Save">
    The shortcut becomes available for matching metadata keys on the same parent type.
  </Step>

  <Step title="Use the shortcut">
    Open the shortcut from any matching metadata field to jump to the external system.
  </Step>
</Steps>

## 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_id`
* `site_id`
* `ticket_id`
* `billing_account_id`
* `external_id`
* `support_url`
* `owner_team`

Avoid storing secrets, passwords, private keys, or access tokens in metadata. Metadata is operational context, not a secret store.

## 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.