> 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/collections/collection-permissions.md).

# Collection Permissions

Collection Permissions allows users to grant permissions to other users and user groups to control who can view, share, edit or have full access to a Collection. Permissions set on a collection will also apply to all assets within that Collection 😍.

👉 **For example:**

The 'Marketing' group is granted 'Can Edit' permission for the 'Sunset 2024' Collection. This means that all members of the 'Marketing' group can view and edit Collection settings and edit all content (images, descriptions) of products within the Collection 'Sunset 2024'.&#x20;

## How to set Collection Permission?

1️⃣ **Access the Collection Detail page:** This is the page that displays detailed content of the Collection you want to share.

2️⃣ **Click 3 dot icon** (on the top - under the Collection name): You switch to the Permission tab and **select 'Edit Permission'** to start setting access rights. You can set access periods to each specific user group.&#x20;

3️⃣ Select '**Add**' to save the settings.

<figure><img src="/files/IQ9eEqLa2cRbNpdtdZ2C" alt=""><figcaption><p>Collection Permission</p></figcaption></figure>

👉 The following permissions are available to be set on the collection:

* **Can View** - Can view the Collection settings and Assets.
* **Can Share** - Can share Collection and Assets with other user groups.
* **Can Edit** - Can edit Collection settings and Assets.
* **Can Add Versions** - Can add versions to the Collection Assets.
* **Full Access** - Full access to the Collection and its Assets.

<figure><img src="/files/xTGSKEyu6PbW1GgF5t8s" alt=""><figcaption><p>Permission Options </p></figcaption></figure>

By setting permissions for Collections, you can ensure asset/information security, assign work effectively, and improve team workflows 😘. Combined with [collection categories](https://support.hivo.co/collections/collection-categories), collection management is a breeze.

If you have any questions, don't hesitate to ask, we're always here to help!


---

# 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/collections/collection-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.
