A device group lets you define shared settings once and apply them to several devices. Devices assigned to the group inherit that group's configuration, so you do not have to configure each device separately.
You can also mark one group as the default for new devices. When a new personal (browser) device is created, or a tablet or phone auto-registers for the first time, Azumuta assigns that default group automatically.
For adding or editing individual devices, see how to add, edit, and delete a device.
To open the device list: go to Management → Devices.
Create a device group
- Go to Management → Devices.
- Click Add group.
- Enter a Name.
- Optionally tick Set as default group for new devices.
- Configure the shared settings as needed, then save.
You need the “manage devices” right to create and edit device groups.
Edit a device group
- Go to Management → Devices.
- Next to the group, open the ⋮ (three-dot) menu.
- Click Edit group.
- Make your changes, then save.
Default group for new devices
On the group form, the checkbox label is:
Set as default group for new devices
Its description is:
Newly created devices are automatically assigned to this group
In the device list, the default group shows the badge Default for new devices.
Changing which group is the default requires the “manage workspace settings” right. If you do not have that right, the checkbox is disabled and a tooltip explains:
You need the "manage workspace settings" right to change this setting
You can still edit other group settings with the “manage devices” right.
When the default applies
The default group is assigned only when a device is created for the first time via:
- A new personal / browser device
- A new tablet or phone auto-registration
It is not retroactive. Devices that already exist keep their current group assignment when you set or change the default.
Manually adding a device from the admin UI does not auto-assign the default group — choose a group when you add the device if you want one.
Identifier-login devices
Multi-user devices that use identifier login follow a different provisioning path. See how to set up an identifier login.