Enrollment Templates
An Enrollment Template is a reusable configuration that lets you onboard many Windows or Linux Agents with a single installation command. Instead of creating one device at a time, you define the approval policy, optional IP match rules, device naming, datasets, profiles, and update policy once — every Agent that runs the template's installation command then enrolls into that template's Director.
Use Enrollment Templates when you are rolling out Agents to more than a handful of endpoints, when you need consistent device names and data collection across a fleet, or when you want approval gating before a new endpoint joins the platform.
Access
Navigate to
Devices — devices already enrolled and managed individuallyTemplates — Enrollment Templates for that platform
Templates are managed per platform: a Windows template enrolls Windows Agents, a Linux template enrolls Linux Agents. The flows on both platforms are otherwise identical.
Templates List
The
Table Columns
| Column | Description |
|---|---|
| Template Name | Identifier set when the template was created |
| Director | Director the template enrolls Agents into |
| Enrolled | Enrolled count over maximum (53/100) or n/Unlimited when no limit is set |
| Pending Approval | Number of enrollment requests awaiting review |
| Time Limit | Validity period; hover for "Expires in X" tooltip, Indefinite when no limit is set |
| Status |
Controls
The toolbar provides a
Status Values
- Enabled — Template is active and accepting enrollments
- Disabled — Template is paused; new Agents cannot enroll until re-enabled
- Expired — Template's time limit has elapsed; no new enrollments accepted
- Limit Reached — Maximum enrollment limit has been hit; no new enrollments accepted
Expired and Limit Reached are computed from the template's settings; you do not set them directly. To re-open enrollment, edit the time limit or maximum limit in
Creating a Template
The creation wizard has six steps. Steps one through four are configurable; step five lets you review and edit any earlier step; step six is terminal and cannot be revisited.
Step 1 — Template Settings
Define the basic identity of the template and the Director it enrolls Agents into.
| Field | Required | Description |
|---|---|---|
| Template name | Y | Unique name, up to 128 characters |
| Set maximum enrollment limit | N | Toggle. When off, enrollments are unlimited. When on, expose a numeric input for the cap. Enrollment stops once this limit is reached. |
| Set template time limit | N | Toggle. When off, the template is valid until disabled or deleted. When on, choose Presets (8 hours, 24 hours, 1 week, 1 month) or Date & Time Range. Validity starts at template creation. |
| Director | Y | Director that enrolled Agents connect to |
| Access token | Y | Director access token that Agents present when enrolling |
Step 2 — Enrollment Settings
Configure how devices are approved and named when they enroll.
Approval method:
Auto approval — All Agents that run the installation command are approved automatically and become devices.Manual approval — An Admin or Owner must review each enrollment request and approve or reject it before the device is created.
Match rules (optional):
Toggle
- Single IP / IP Block
- IP Range
- CIDR
Multiple rules are evaluated as OR; an Agent matching any rule passes the filter.
Fallback behavior (Auto approval + match rules only):
When the approval method is Auto and match rules are enabled, choose what happens to Agents that do not match any rule:
Require manual approval — request is queued for an Admin or Owner to reviewReject automatically — request is denied without further review
This field is hidden when approval method is Manual or when no match rules are defined.
Device naming structure:
Use host name — the Agent's host name becomes the device nameUse template — provide a naming template using the variableshost.domain,host.name,host.fqdn,host.ipaddress,unique.id(for example{host.domain}.{host.name}producesvirtualmetric.device01)
When the same template name resolves to a duplicate, a sequential number is appended (vm-device-1, vm-device-2).
Step 3 — Data Configuration
Select the datasets and profiles that the enrolled Agents will collect. The selection works the same way as in the standard device creation wizard. For details on datasets and profiles, see Datasets and Profiles.
Step 4 — Update Management
Configure the auto-update policy that enrolled Agents will use. The fields and behavior match the Agent auto-update configuration: pick a mode (Manual or Auto), method (Immediate or Scheduled), and either a cron expression or a polling interval.
Step 5 — Review and Create
The review step lists each prior step with the values you entered and a
Step 6 — Complete Configuration
The final step shows the installation command that enrolls Agents into this template. Copy and run the command on each endpoint that should be enrolled — PowerShell on Windows, Bash on Linux. The command is also available later from the template's
This step has no
Template Detail
Clicking a template name from the list opens the detail page. The page has five tabs.
Template Settings Tab
Read-only summary plus inline edit. Fields shown:
- Template name, Maximum Enrollment Limit, Template Time Limit
- Director (read-only — cannot be changed after creation)
- Status, Enrolled Devices (used / max), Created, Last Updated
A banner at the top of the page surfaces the current state:
| Condition | Banner | Action |
|---|---|---|
| Pending enrollment requests exist | Info — "Pending enrollment requests" with count | |
Status = Limit Reached | Warning — explains the cap was hit | Edit max limit in Template Settings to continue |
Status = Expired | Warning — shows the expiration date | Extend the time limit in Template Settings |
Enrollment Settings Tab
Shows the installation command, approval method, match rules, fallback behavior, and device naming structure. Use the
Data Configuration Tab
Manages dataset and profile selection. Use the
Update Management Tab
Shows the auto-update policy applied to Agents enrolled through this template. Use the
Enrollment Requests Tab
Lists all enrollment requests received by this template. See Enrollment Requests for details.
Enrollment Requests
When an Agent runs the template's installation command, it sends an enrollment request to the Director. The request's outcome depends on the template's approval method and match rules:
| Approval method | Match rules | Outcome |
|---|---|---|
| Auto | None | Approved automatically — device is created. |
| Auto | Defined | Matching devices are approved automatically; non-matching devices follow the configured fallback behavior (manual approval queue or automatic rejection). |
| Manual | Any | All requests queue for review. An Admin or Owner approves or rejects each one. |
Rejected requests do not create a device. Pending requests can be approved or rejected from the
Requests Table
| Column | Description |
|---|---|
| Device Name | Name resolved from the device naming structure |
| IP Address | Source IP address of the enrolling Agent |
| Enrollment Requested | Timestamp when the request was received |
| Action Time | Timestamp when the request was approved or rejected |
| Status | |
| Action Taken by | User who approved or rejected the request |
The table supports search and pagination. Bulk approve and bulk reject actions are available when multiple pending requests are selected.
Request Drawer
Clicking a device name opens a side drawer with full request details:
Request Details: Device Name, Enrollment Requested, Status
Device Details: Host Name, Host FQDN, IP Address, MAC Address, Operating System, OS Version
For pending requests, the drawer provides
Template Actions
Each row in the templates list and the template detail page expose an actions menu (⋮):
Manage template — open the detail pageClone template — create a copy namedCopy of <name>with all settings preservedDisable template — pause new enrollments without deleting the templateEnable template — resume a previously disabled templateDelete template — permanently remove the template
Disable
Disabling a template stops new enrollment requests and prevents new devices from being created through it. Existing devices that were already enrolled through the template are not affected. A confirmation modal explains the consequence; you can re-enable the template at any time.
Delete
Deleting a template is permanent.
Deleting a template removes the template and all of its pending enrollment requests. Existing devices that were previously enrolled through the template remain on the platform and continue to operate. New Agents can no longer enroll using the deleted template's installation command.
A confirmation modal requires you to confirm before the template is removed.