> For the complete documentation index, see [llms.txt](https://docs.fenixpyre.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/integrations/egnyte/how-to-configure-user-policy-protected-folder.md).
# How to configure user policy (Protected folder)
This guide for adding an Egnyte folder as a protected folder on FenixPyre Dashboard
1. **Log into FenixPyre Dashboard**
* Open your browser and go to the **FenixPyre Dashboard**.
* Enter your **Admin credentials** and sign in.
2. **Navigate to User Policy**
* Click on the **User Policy** section in the left menu.
User Policy Page
3. **Select the User Policy to Modify**
* Select the respective policy if applying the protected folder to a specific user group.
* If applying to **all users**, select the **Default Policy**.
4. **Go to the Protected Folder Tab**
* In the **User Policy settings**, navigate to the **Protected Folder** tab.
5. **Add the Protected Folder Path**
* Click on **Protected Folders**
* Select Type as **"Egnyte Web"** from the dropdown.
* Enter the folder path in the required format:
```
\\\
```
* Example:
```
\\fenixpyre.egnyte.com\Shared\Documents\Demo
```
6. **Save changes**
* and the above folder will be added as a protected folder
---
# 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.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/integrations/egnyte/how-to-configure-user-policy-protected-folder.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.
