> For the complete documentation index, see [llms.txt](https://docs.guardware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guardware.com/documentation/partner-portal/partner-portal-detailed-guides/templates.md).
# TEMPLATES
Templates bundle reusable compliance and security settings for consistent organisation setup. They can define sensitive data types, PROTECT policies, and INSIGHT device settings. Create templates at the partner level, then assign them to one or more organisations.
1. Navigate to **ORGANISATION** and click **Assign Template**.
2. Select the appropriate template from the dropdown.
3. Click **Assign** to assign the template to the organisation.
{% hint style="info" %}
Templates must be created before the assignment. To create a template, navigate to the relevant section and set up your first template.
* [**Data Type Templates**](#data-types)
* [**PROTECT Templates**](#protect)
* [**INSIGHT Templates**](#insight)
{% endhint %}
## DATA TYPES
Data Type Templates are reusable configurations of the Data Types used by GuardWare to identify sensitive information during scanning. Partner Admins and Partner Users can create templates containing the Data Types required for a particular organisation, and then reuse those templates instead of configuring Data Types individually for every new organisation.
### Data Type Template
{% stepper %}
{% step %}
Navigate to **Data Types** > **Data Type Template** and click **+New Data Type Template**.
{% endstep %}
{% step %}
Enter a **Template name** and an optional **Description**. If you wish to import configuration from existing templates, select **Import Settings** and choose a template from the dropdown. Click **Continue** to proceed.
{% endstep %}
{% step %}
Select the data types from the list; you can use the search or filter function to find specific data types quickly.
{% endstep %}
{% step %}
Click **Save Template** to create the template.
{% endstep %}
{% endstepper %}
Edit a Data Type Template
{% hint style="warning" %}
You cannot modify or delete data types created by the system or super admins.
{% endhint %}
1. Navigate to **Data Types** > **Data Type Templates**.
2. Click :pencil: **Edit** to update the template name, description, and assigned data types.
3. Click **Save Template** to update changes.
Add or Remove Data Types to Template
1. Navigate to **Data Types** > **Data Type Template**.
2. Click an entry in the **Data Type** column or click **Add Data Type** to open the side panel.
3. Click **All** to select all, or select individual data types to assign or unassign them.
4. Click **Update Template** to apply changes.
{% hint style="info" %}
Click **Add Data Type**, then select **Assigned** to view data types currently assigned to the selected template.
{% endhint %}
Delete a Data Type Template
1. Navigate to **Data Types** > **Data Type Templates**.
2. Click **Delete** :trash-can: to delete the selected template.
3. Click **OK** again to confirm**.**
### Data Type
Data types define the specific categories of sensitive information GuardWare scans for within an organisation. Only create a new data type if the predefined data types in the library don't cover the sensitive data required for your organisation.
{% stepper %}
{% step %}
Navigate to **Data Types** > **Data Type** and click **+New Data Type**.
{% endstep %}
{% step %}
Follow the procedures here to [**create a custom data type**](/documentation/management-console/data-governance/data-type.md#create-a-data-type).
{% endstep %}
{% endstepper %}
Edit a Data Type
1. Navigate to **Data Types** > **Data Type** and click the **Edit** :pencil: icon.
2. Rename the data type, refine parameters and assign or remove its subtypes the same way as when **creating a data type**.
Delete a Data Type
1. Navigate to **Data Types** > **Data Type** and click the **Delete** :trash-can: icon.
2. Click **Delete** to remove the data type or **Cancel** to call off the operation.
## PROTECT
PROTECT templates define the protection policies applied to an organisation. A PROTECT template is made up of three components: User Policies, Application Settings, and Avoid Folders. Each component is configured independently and combined into a template that can be assigned to one or more organisations.
### User Policy Template
User policies determine which features and actions are available in the PROTECT Agent, giving administrators control over the end-user experience.
{% stepper %}
{% step %}
Navigate to **PROTECT** > **User Policies** and click **+New User Policy**.
{% endstep %}
{% step %}
Enter the **Policy Title** and give a **Description**. If you want to duplicate a user policy, select the existing policy from the **Clone from Existing Policy** dropdown.
{% endstep %}
{% step %}
Enable **Detours** if you want to prevent protected files opened in Word, Excel, and PowerPoint from being automatically saved and synced to OneDrive or SharePoint.
Enable **Private Mode** to allow users to use private or incognito browsing. Disable it to prevent users from using private or incognito browsing.
{% endstep %}
{% step %}
Configure the file protection actions; to learn more about these settings or how to configure them in detail, refer to the [**User Policies documentation**](https://docs.guardware.com/documentation/protect/encryption-and-policies/user-policies).
{% endstep %}
{% step %}
Click **Save** to apply configurations.
{% endstep %}
{% endstepper %}
Edit User Policy Template
1. Navigate to **PROTECT** > **User Policies**.
2. Search for the policy and click **Edit** ✎ under **ACTIONS** to update the policy.
3. Update the policy and click **Save**.
Delete User Policy Template
1. Navigate to **PROTECT** > **User Policies**.
2. Search for the policy and click **Delete** :trash-can:.
3. Click **Delete** to remove the policy.
### Application
Define which applications can open, edit, and save protected files. These applications ensure PROTECT can encrypt files when users save or export them in different formats, ensuring only approved applications can access or modify protected content.
#### Create an Application List
The Application List contains predefined application policies. Applications are first added to the list, which serves as the pool of available apps that the user can add to the template.
{% stepper %}
{% step %}
Navigate to **PROTECT** > **Application** > **Application List** and click **+New Application**.
{% endstep %}
{% step %}
Enter the name of the executable file in **Executable Name**, the family of application it belongs to in **Application Suite** (optional), and the directory where the executable is in **Folder Path**.
Click :square-plus: to add the directory to the **Folder Path Selected** list.
{% endstep %}
{% step %}
Define which file extensions the application can encrypt or decrypt.
{% endstep %}
{% step %}
Enable **Network Drive Support** if the application needs to access encrypted files on network drives.
{% endstep %}
{% step %}
Click **Save**. The app will now appear in the **Application List**.
{% endstep %}
{% endstepper %}
Edit an Application List
1. Navigate to **PROTECT** > **Application** > **Application List**.
2. Click :pencil: **Edit** on the desired entry to update its details.
3. Click **Save** to apply changes.
Delete an Application List
1. Navigate to **PROTECT** > **Application** > **Application List**.
2. Click :trash-can: **Delete** to remove the application from the list.
3. Confirm deletion by clicking **Delete**.
#### Create an Application Template
{% hint style="warning" %}
An **Application List** must be created before you can create an **Application Template**.
{% endhint %}
Applications list can be grouped into a template that can be assigned across organisations.
{% stepper %}
{% step %}
Navigate to **PROTECT** > **Application** > **Application Template**.
{% endstep %}
{% step %}
Enter a **Template Name** and a **Description**. If you want to duplicate a setting, select one from the **Import Settings** dropdown and click **Continue**.
{% endstep %}
{% step %}
Select the applications from the list to assign them to the template. You can search for a specific application from the search bar to find it quickly.
{% endstep %}
{% step %}
Click **Save Template** to create the Application template.
{% endstep %}
{% endstepper %}
Edit an Application Template
1. Navigate to **PROTECT** > **Application Template**
2. Click **Edit** on the desired entry to update its details.
3. Click **Save** to apply changes.
Delete an Application Template
1. Navigate to **PROTECT** > **Application** > **Application Template**.
2. Click **Delete** :trash-can: to remove the application template from the list.
3. Confirm deletion by clicking **Delete**.
### Avoid Folders
The Avoid Folders section lets you define directories that can be **excluded from encryption**.\
Files stored in these folders will not be encrypted by PROTECT, even if they include sensitive words or match any pre-defined data type.
{% hint style="danger" %} The following entries are system-defined and must not be modified or removed:
Directory
Folder
C:\Users*\AppData
Mandatory App Data
C:\Program Files
Program Files
C:\Program Files (x86)
Program Files (x86)
C:\Windows
Windows
{% endhint %}
#### Create an Avoid Folder List
If the folder you want to exclude is not included in the existing Avoid Folder List, create a new folder list and specify the folder path to exclude from protection.
{% hint style="warning" %}
An Avoid Folder List must be created before creating an Avoid Folder Template.
{% endhint %}
{% stepper %}
{% step %}
Navigate to **PROTECT** > **Avoid Folders** > **Avoid Folder List** and click **+New Avoid Folder**.
{% endstep %}
{% step %}
Enter a **Title** for the template and specify the folder path to exclude in **Directory**.
{% endstep %}
{% step %}
Click **+ Add Sub Folder** to add a subfolder within the specified directory. You can add multiple subfolders.
Although the main directory is excluded from encryption, subfolders added here continue to follow the normal encryption rules. Use this option when you need to exclude a directory while continuing to protect specific subfolders containing sensitive or regulated information.
{% endstep %}
{% step %}
Click **Save** to create the list.
{% endstep %}
{% endstepper %}
Edit Avoid Folder List
1. Navigate to **PROTECT** > **Avoid Folders** > **Avoid Folder List**.
2. On the desired entry, click **Edit** :pencil: to make any changes.
3. Click **Save** to apply configurations.
Delete Avoid Folder List
1. Navigate to **PROTECT** > **Avoid Folders** > **Avoid Folder List**.
2. On the desired entry, click **Delete** :trash-can: to delete the list.
3. Confirm deletion by clicking **Delete**.
#### Create an Avoid Folder Template
{% stepper %}
{% step %}
Navigate to **PROTECT** > **Avoid Folders** > **Avoid Folder Template** and click **+New Avoid Folder Template**.
{% endstep %}
{% step %}
Enter a **Template Name** and a **Description**. If you want to duplicate a setting, select one from the **Import Settings** dropdown and click **Continue**.
{% endstep %}
{% step %}
Select the avoid folder directories by clicking the checkboxes.
{% endstep %}
{% step %}
Click **Save Template** to confirm the assignment.
{% endstep %}
{% endstepper %}
Add Avoid Folder
1. Navigate to **PROTECT** > **Avoid Folders** > **Avoid Folder Template**.
2. Click **Add Avoid Folder** to open the side panel.
3. Click **All** and select to assign or unselect to unassign directories by clicking the checkbox.
4. Click **Update Policy** to apply changes.
{% hint style="info" %}
Select **Assigned** to view data types currently assigned to the selected template.
{% endhint %}
Edit Avoid Folder Template
1. Navigate to **PROTECT** > **Avoid Folders** > **Avoid Folder Template**.
2. Click **Edit** :pencil: to make any required changes.
3. Click **Save Template** to save changes.
Delete Avoid Folder Template
1. Navigate to **PROTECT** > **Avoid Folders** > **Avoid Folder Template**.
2. Click **Delete** :trash-can: to delete the template.
3. Confirm deletion by clicking **Delete**.
## INSIGHT
INSIGHT templates define the policies and configurations applied to devices of an organisation. Each component is configured independently into a template that can be assigned to one or more organisations.
### Advanced Setting
Advanced Settings function as the central control point for how monitoring is configured and enforced across the organisation. These settings determine how INSIGHT operates on end-user devices. An Advanced Setting Template lets this configuration be defined once and applied to one or more organisations, instead of being set up individually each time.
{% stepper %}
{% step %}
Navigate to **INSIGHT** > **Advanced Setting** and click **+New Advanced Setting**.
{% endstep %}
{% step %}
Enter **Setting Name** and **Description**. If you want to duplicate a user policy, select the existing policy from the **Copy Settings From** dropdown.
{% endstep %}
{% step %}
Check the box if you wish to set this Advanced Setting as the default; then click **Next**.
{% endstep %}
{% step %}
Configure the Advanced Settings by clicking **+Add Setting** button.
{% endstep %}
{% step %}
Click **Review & Save** to review the settings and click **Save** to create the advanced setting.
{% endstep %}
{% endstepper %}
View Advanced Setting Details
1. Navigate to **INSIGHT** > **Advanced Setting**.
2. On the desired template, click :eye: **View Details**.
3. Click :square-plus: to expand and view the Advanced Setting configurations.
Edit Advanced Setting
1. Navigate to **INSIGHT** > **Advanced Setting**.
2. On the desired Advanced Setting, click :pencil: **Edit** to make any required changes.
3. Click **Update & Save** to apply changes.
Delete Advanced Setting
1. Navigate to **INSIGHT** > **Advanced Setting**.
2. On the desired Advanced Setting, click :trash-can: **Delete** to open the confirmation window.
3. Click **Yes, Delete it** to delete the Advanced Setting.
### User Policy
User Policies define how user activities are monitored, governed, and controlled within the organisation, helping organisations monitor and prevent risky actions such as accessing restricted applications, transferring sensitive data, or using unauthorised devices. A User Policy Template lets this configuration be defined once and applied to one or more organisations, instead of being set up individually each time.
{% stepper %}
{% step %}
Navigate to **INSIGHT** > **User Policies** and click **+New User Policy**.
{% endstep %}
{% step %}
Follow the procedures here [**to create a User Policy**](/documentation/insight-v4/insight-v5/user-policies.md#add-a-user-policy).
{% endstep %}
{% endstepper %}
View User Policy
1. Navigate to **INSIGHT > User Policies**.
2. Find the policy you want to view, and click :eye: **View** in the **ACTIONS** column.
3. The policy overview page opens, where you can review its configuration, including applied rules, selected activities, and enforcement settings.
Configure Data Types
1. Navigate to **INSIGHT > User Policies**.
2. Find the policy whose data type you want to update, and click :database: **Data Types** in the **ACTIONS** column.
3. Find the data type you want to update and click **Edit** in the **ACTION** column.
4. Update the details and click **Apply To This Row**.
5. You can also add or delete any data type.
6. Click **Submit** after applying your changes.
Edit User Policy
1. Navigate to **INSIGHT > User Policies**.
2. Find the policy you want to edit, and click :pen-to-square: **Edit** in the **ACTIONS** column.
3. Edit the details and click **Confirm**.
Delete User Policy
1. Navigate to **INSIGHT > User Policies**.
2. Find the policy you want to delete and in the **ACTIONS** column, click the :trash-can: **Delete** icon.
3. Click **Yes, delete** in the confirmation alert.
### Working Days & Hours
The Working Days section shows your organisation’s official working days and hours. These settings help INSIGHT distinguish between working and non-working time. A Working Days & Hours Template lets this configuration be defined once and applied to one or more organisations, instead of being set up individually each time.
{% stepper %}
{% step %}
Navigate to **INSIGHT** > **Working Days & Hours** and click **+Add New Template**.
{% endstep %}
{% step %}
Provide a **Template Name** and a **Description** to the template.
{% endstep %}
{% step %}
Set the working days and working hours by clicking the checkboxes.
{% endstep %}
{% step %}
Click **Save Template** to set the Working Days & Hours time.
{% endstep %}
{% endstepper %}
Edit Working Days & Hours
1. Navigate to **INSIGHT** > **Working Days & Hours**.
2. Click :pencil: Edit and adjust the days and time of the desired template.
3. Click **Update Template** to apply changes.
Delete Working Days & Hours
1. Navigate to **INSIGHT** > **Working Days & Hours**.
2. Click :trash-can: Delete to open a confirmation window of the desired template.
3. Click **Delete** to remove the template.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.guardware.com/documentation/partner-portal/partner-portal-detailed-guides/templates.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
