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

# ITSM Provisioning Templates

> Browse, filter, create, and edit IT provisioning templates for onboarding and offboarding workflows, organized by workflow type.

This page lists all provisioning templates for IT onboarding and offboarding workflows. Navigate to it at `/it/jml/templates`.

## Overview

The Provisioning Templates page presents a tabbed view of templates grouped by workflow type (Onboarding / Offboarding). A search box filters by template name, description, or role type. The table shows Name, Role Type, Task Count, Status (Active/Inactive), and Default badge. The actions menu per row provides Edit (navigates to `/it/jml/templates/:id`) and Duplicate/Delete (currently disabled in the UI).

## Who it's for

This route is protected by `IT_PERMISSIONS.VIEW` (`it.view`) via the module-level `ITViewGuard`. No additional per-route permission gate exists beyond the module guard.

## Before you start

* No prerequisites. Templates load automatically.

## Steps

1. Navigate to **IT > JML > Provisioning Templates**, or go directly to `/it/jml/templates`.
2. Select the **Onboarding** or **Offboarding** tab.
3. Use the search box to filter templates by name, description, or role type.
4. Click the actions menu (three dots) on a row and choose **Edit** to modify the template.
5. Click **New Template** to create a new provisioning template.

## Key concepts

* **Workflow type** — `onboarding` or `offboarding`; used to filter templates shown on each tab.
* **Role type** — optional restriction of a template to a specific employee role.
* **Task count** — the number of task definitions embedded in the template.
* **Default** — when flagged, this template is auto-selected when no specific template is chosen for that workflow type.
* **Active / Inactive** — inactive templates cannot be selected for new workflow instances.

## Viewing and editing a template

The Template Details page (`/it/jml/templates/:id`) allows editing of the template name, description, role type, active flag, default flag, and task definitions. It includes a Delete button with confirmation dialog. On save, the template is updated in place; on delete, the user is redirected to `/it/jml/templates`.

**Note:** The alternate route `/it/changes/templates/:id` loads `ITChangeTemplateDetailPage` for change management templates (see Change Templates).

Permission required: `IT_PERMISSIONS.VIEW` (`it.view`) via the module-level `ITViewGuard`. No additional per-route gate.

1. Navigate to **IT > JML > Provisioning Templates**, open the actions menu on a row, and click **Edit**, or navigate directly to `/it/jml/templates/:id`.
2. Edit the **Template Name**, **Description**, or **Role Type** as needed.
3. Toggle **Active** or **Default Template** flags.
4. In **Task Definitions**, click **Add Task** to add tasks, or use the remove icon to delete existing tasks.
5. Click **Save Changes** to persist updates.
6. To delete the template, click **Delete Template** and confirm in the dialog.

**Key fields:**

* **workflow\_type** — read-only on this page; set at template creation (`onboarding` or `offboarding`).
* **is\_active** — controls whether the template can be selected for new instances.
* **is\_default** — auto-selects this template when no specific template is chosen.
* **due\_days\_offset** — days from workflow start date by which each task is due.

## Creating a template

The New Template page (`/it/jml/templates/new`) allows IT administrators to define reusable onboarding or offboarding templates. Templates contain basic metadata (name, description, workflow type, role type, active/default flags) and a list of task definitions. Each task has a title, category, required flag, and a due-days offset from the workflow start date. On success the user is redirected to the Provisioning Templates list at `/it/jml/templates`.

Before you start: decide whether the template applies to onboarding or offboarding; have the task list ready including categories and typical due timelines; determine if this should be the default template for its workflow type and role type.

1. Navigate to **IT > JML > Provisioning Templates** and click **New Template**, or go directly to `/it/jml/templates/new`.
2. Enter a **Template Name** (required).
3. Optionally enter a **Description** and a **Role Type**.
4. Select **Workflow Type**: Onboarding or Offboarding.
5. Toggle **Active** (on by default) and **Default Template** as needed.
6. Under **Task Definitions**, click **Add Task** to add tasks one by one.
   * For each task: enter a title, choose a category (`account`, `access`, `equipment`, `software`, `security`, or `other`), set the due-days offset, and mark whether it is required.
7. Review the sidebar summary (workflow type, task count, required task count).
8. Click **Create Template** to save. On success you are redirected to the Provisioning Templates list.

**Key concepts:**

* **Workflow type** — `onboarding` or `offboarding`; determines which dashboard the resulting instances appear on.
* **Task category** — groups tasks by domain: `account`, `access`, `equipment`, `software`, `security`, `other`.
* **due\_days\_offset** — number of days from the workflow start date by which a task should be completed.
* **is\_default** — when true this template is used automatically when no specific template is selected for the workflow type.

## Related

<Columns cols={2}>
  <Card title="IT Service Management" icon="headset" href="/it/overview">
    IT Service Management overview.
  </Card>

  <Card title="Governance & parity" icon="scale-balanced" href="/governance/index" />
</Columns>

<Note>
  This page documents shipped product behavior. It is not medical, legal, or
  billing advice. Verify against your organization's policies and applicable
  regulations before using it for clinical, compliance, or billing decisions.
  Protected health information (PHI) shown in the product is governed by your
  tenant's access controls and is never exposed in this documentation.
</Note>

<Accordion title="Documentation sources">
  * src/routes/it.tsx
  * src/cores/it/pages/onboarding/ProvisioningTemplatesPage.tsx
  * src/cores/it/pages/onboarding/ProvisioningTemplateDetailPage.tsx
  * src/cores/it/pages/onboarding/NewProvisioningTemplatePage.tsx
  * src/cores/it/hooks/useOnboardingTemplates.ts
  * src/cores/it/hooks/useOnboardingTemplateMutations.ts
  * src/cores/it/types/onboarding.ts
</Accordion>