> For the complete documentation index, see [llms.txt](https://support.hivo.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.hivo.co/library/folder-management-tools/folder-permissions.md).

# Folder Permissions

Folder Permissions in an important feature that allows users to set and control who can set asset permissions at a folder level.

{% hint style="info" %}
**Why do we need Folder Permission?**

* ***Data security:** Prevent unauthorized access to important files.*
* ***Access management:** Allow users to have different access rights according to their roles and tasks.*
* ***Sensitive data protection:** Prevent important files from being accidentally modified or deleted.*
  {% endhint %}

### How to set up Folder Permissions

The process for setting [Asset Permissions](/assets/assets-permission.md) on all assets inside a folder is:

1. **Switch the Library to Folder View or Tree View** by clicking the View Mode Button (top right corner of the Library)

<figure><img src="/files/qSRq8XobnMvvdsAMgXYl" alt=""><figcaption><p>Switch to Library view mode</p></figcaption></figure>

2. **Open the Folder Actions** dialog box: Right-click on the folder you want to set access rights to and Select "**Edit Permission**".

<figure><img src="/files/HgEP2LS7EY9UJZgMiOsN" alt=""><figcaption><p>Open the Folder Action menu</p></figcaption></figure>

3. **Set permissions**: Select User/Group and corresponding permissions&#x20;

All permission tiers grant viewing permissions for the folder. Here’s a breakdown of the additional permissions each tier provides:&#x20;

* **Can View:** Users can view the asset and its versions.&#x20;
* **Can Share**: Users can share the asset with others.&#x20;
* **Can Edit:** Users can make changes to the asset.&#x20;
* **Add Versions:** Users can add new versions to the asset.&#x20;
* **Full Access:** Users have all permissions, including viewing, sharing, editing, and adding versions.

<figure><img src="/files/XYd8ZajCRWIrMXv41jhM" alt=""><figcaption><p>Set permission</p></figcaption></figure>

4\. Click “**Add**” to add permissions to the User/Group Apply and click “**Submit**” to apply.

<figure><img src="/files/Fso6A84mjqsvDjh66oSk" alt=""><figcaption><p>Add Foler Permission</p></figcaption></figure>

👉 For example, Human Resources can create a folder containing employee records, allowing only the human resources department and management to access or Share Project can create a folder to share the project with collaborators, allowing only them to view and edit files related to that folder.

{% hint style="info" %}

* ***Inheritance:** The access rights of the parent folder can be inherited by the child folders.*
* ***Group:** You can create user groups to manage access rights more easily.*
  {% endhint %}

By using Folder Permission effectively, you can protect your data from unauthorized access and enhance the security of your system.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.hivo.co/library/folder-management-tools/folder-permissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.