A template is a saved set of user-field values you apply to many users at once. Instead of editing each user one by one, you define the values on a template and apply it to a batch of users and groups.
Overview
A template has two parts: the field values and a per-field Override toggle that decides whether each value is actually pushed.
What it does
The Override toggle separates "this value is set on the template" from "this value should overwrite the target's value".
| Override state | What happens on apply |
|---|---|
| On | The template's value replaces the target user's value. |
| Off | The target user's current value is preserved. The template's value is ignored. |
Override is off by default on most fields. Use it liberally in the off state: the point of templates is to push the deltas, not the defaults. A focused template with three fields toggled on is easier to reason about than one with thirty.
Choosing the targets
A template is applied to the users you name, the members of the groups you name, or - with the Apply to all users switch - to everyone on the PBX. Targets are resolved when you run the apply action, not when you save the template, so a group that gains a member, or a user created after the switch was turned on, is covered by the next apply without touching the template.
Turning the switch on hides the two target lists but keeps them: turn it off and the previous selection comes back.
Apply overwrites the marked fields on every target user with no per-user opt-out and no rollback, so confirm the targets and the override list first. Templates are batch operations, not standing policies: nothing is applied until you run the apply action.