Introduction
The Custom fields tab shows every custom field in your organization and lets you set group-level default values. Any value set here cascades down to all devices in the group — unless a device has its own override.
For a full explanation of custom fields, how to create them, and how inheritance works across all scopes, see Workspace → Custom Fields.
Group Custom Fields
Navigate to a group's settings (Devices → [group name] → Custom fields).
The table has three columns:
Field name — the field's name as defined in Workspace. Fields with a value inherited from the organization show "Inherited from [org name]" beneath the name.
Description — the optional description set when the field was created.
Field value — the value currently active at this group level. Fields with no value set at any level show
--.
Use the Search custom fields bar to filter by name — useful when you have many fields defined globally.
Setting a Group-Level Value
Click the ⋮ menu at the end of the row.
Click Edit.
Enter the value in the Field value field.
Click Update custom field.
⚠️ WARNING: Setting a value here overrides the global default from Workspace for all devices in this group. Devices with their own device-level override are unaffected — they keep their own value.
Once set, all devices in this group use this value unless they have their own device-level override.
💡 TIP: Group-level custom fields are the right place for anything that's the same for every device in a group but varies between groups — client credentials, AV tokens, deployment keys. Set it once at the group level and every device inherits it automatically.
Clearing a Group-Level Value
To revert a field back to the global default:
Click the ⋮ menu on the row.
Click Clear value.
The field returns to inheriting from the organization's global default. If no global default is set, it returns to --.
Copying a Field Value
Each row has a copy icon. Click it to copy the current field value to your clipboard — useful when pulling credentials or tokens stored at the group level.
How Inheritance Works
Custom fields cascade from most general to most specific. Level uses the value from the most specific scope that has one:
Organization (global default, set in Workspace → Custom Fields)
Group (set here)
Device (set in Device Details → Custom Fields)
A field with "Inherited from [org name]" means this group hasn't set its own value — it's using the global default. A field with a value but no inherited label was set directly at this group level.
When an automation or script runs on a device in this group, it receives whichever value is most specific for that device.
FAQ
If I set a group-level value, will all devices in this group use it immediately? Yes. Level resolves custom field values at execution time. The next time an automation or script runs on a device in this group, it'll pick up the group-level value — unless that device has its own override.
A device in this group has its own custom field value set. Does the group value affect it? No. Device-level values take precedence over group and global defaults. The device keeps its own value until it's cleared at the device level. See Device Details → Custom Fields.
Can I create new custom fields from this view? No. Fields are created in Workspace → Custom Fields. This view lets you set group-level values for existing fields only.
Who can see admin-only fields? Only organization administrators can see or edit the values of fields marked Admin only. Other technicians can see that the field exists, but the value is hidden.