---
title: Folder sharing and access
product: Unity Asset Manager
canonical: https://docs.unity.com/en-us/asset-manager/folder-sharing-access
last_updated: 2026-11-17
generated_at: 2026-11-18T09:54:15.571Z
locale: en-us
---

# Folder sharing and access

> Understand the roles, inherited access, and visibility that apply when you share an Asset Manager folder with users or groups.

Understand how folder sharing affects access in Asset Manager. This page explains the roles that recipients get on a shared folder, how access is inherited, and what recipients can see.

For the steps to share a folder, refer to [Share a folder](/asset-manager/share-folder.md).

## Roles on a shared folder

When you share a folder, you give the people and groups that you add one of the following roles for that folder: **Viewer**, **Consumer**, or **Contributor**. Everyone you add at the same time gets the same role. In the share dialog, these roles appear as the access levels **Can view**, **Can download & comment**, and **Can edit**. A recipient's folder role gives them the same permissions as that role in the project, but only for the shared folder. For the permissions of each role, refer to [Asset Manager user roles](/asset-manager/org-project-roles.md).

Each role gives the following permissions on a shared folder:

* **Viewer**
  * Can see asset previews and metadata.
  * Can't download files.
  * Can't comment on or annotate assets.
* **Consumer**
  * Can download assets and their dependencies.
  * Can run Optimize and Convert.
  * Can comment on and annotate assets.
  * Can't share folders.
* **Contributor**
  * Can create, edit, and delete assets and folders.
  * Can't share folders.

## Inherited access

A share applies to all subfolders and assets inside the folder, including assets that you add later.

A recipient's effective role is the most permissive role they get from any source, whether through project membership or a folder share. Sharing only adds access. For example, if someone has the Contributor role from a share on a parent folder, sharing a subfolder with them as a Viewer doesn't lower their role.

## What recipients can see

Recipients can see the shared folder and everything inside it. If a recipient's only access comes from this share, they don't see other folders or assets in the project. If someone adds content next to the shared folder later, that content stays hidden unless you share it too. A recipient who also has access through project membership or a share on a parent folder still sees everything that access covers.

Recipients can also see the dependencies of an asset. They can open a dependency only if they have access to the project or folder that contains it.

Recipients find shared folders in the **Shared with me** section of the navigation, which lists the folders that other projects shared with them. They open a shared folder the same way they open their own projects. To keep the list tidy, recipients can hide a shared folder and show it again later.

## Additional resources

* [Share a folder](/asset-manager/share-folder.md)
* [Asset Manager user roles](/asset-manager/org-project-roles.md)
* [Manage access to your project](/asset-manager/manage-project-access.md)
* [Asset Dependencies](/asset-manager/asset-dependencies.md)
