> 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/protect/protection-scope/excluded-folders.md).
# Excluded Folders
The **Excluded 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 predefined Data Type.
Some default directories are preconfigured and should not be removed, as they are required for proper system functionality.
{% hint style="info" %}
Use this feature carefully to avoid accidental exposure of sensitive data.
{% endhint %}
### **Add a Directory to Exclude**
1. Navigate to **PROTECT > Protection Scope > Excluded Folders.**
2. Click **+Add New Directory**.
3. In **Title**, enter a name for this exclusion rule. Example: Accounting Temp Folder.
4. In **Directory,** enter the full directory path that should be excluded from encryption.\
Example:\
`C:\Users\Public\AccountingTemp\`
5. In **Sub Folders**, click **+** and add a complete path of subfolders within the directory that **must continue to be encrypted**. These subfolders override the exclusion rule of the folder.\
\
While the main directory is excluded from encryption, any subfolder added here will **continue to follow normal encryption rules**. This allows you to exclude a directory for operational needs while still protecting specific subfolders that contain sensitive or regulated information.\
\
Use the **+** button to add multiple subfolders.\
{% hint style="info" %}
You must enter a complete path in the **Directory** and **Sub Folder**.
{% endhint %}
**Example:**\
If you add `C:\CompanyData\TempProcessing\` as Directory and specify `C:\CompanyData\TempProcessing\Inbound\` and `C:\CompanyData\TempProcessing\Archive\` as subfolders, all other subfolders within `TempProcessing` will not be encrypted, while only these two specified subfolders will be encrypted.
* `C:\CompanyData\TempProcessing\` → **Not encrypted**
* `C:\CompanyData\TempProcessing\Inbound\` → **Encrypted**
* `C:\CompanyData\TempProcessing\Archive\` → **Encrypted**
* `Other sub folders inside TempProcessing` → **Not Encrypted**
6. Click **Save**.
The directory will appear in the **Directory List**, where it can be edited or removed later.
### Edit a Directory
1. Navigate to **PROTECT > Protection Scope > Excluded Folders.**
2. Search for the directory to edit and click the **Edit** icon in the **ACTIONS** column.\
3. Update the necessary information and click **Save**.
### Delete a Directory
1. Navigate to **PROTECT > Protection Scope > Excluded Folders.**
2. Search for the directory to delete and click the **Delete** icon in the **ACTIONS** column.
3. Click **Delete** in the Confirmation Alert.
---
# 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/protect/protection-scope/excluded-folders.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.
