> For the complete documentation index, see [llms.txt](https://docs.roboflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roboflow.com/datasets/manage/project-folders/project-folder-permissions.md). # Project Folder Permissions Control which workspace members can view and edit projects within a folder using folder permissions. {% hint style="info" %} Project folder permissions is a premium feature offered to select customers on our Enterprise plan. For more details on feature availability, see the [pricing page](https://roboflow.com/pricing). To get access to permissions for project folders, [talk to our sales team.](https://roboflow.com/sales) {% endhint %} Folder permissions provide a way to control who in your workspace can view and edit projects within specific folders in your workspace. This helps ensure team members can focus on the projects relevant to their work while keeping other data secure. It can also be used to compartmentalize data access within an organization to specific teams and people. ### How to Set Project Folder Permissions Within the Roboflow app, click on the three dots next to a given project folder and select the "Set Permissions" button on the menu.

A window will appear where you will be able to select a general access level. * **Anyone:** Everyone in your workspace will be able to access the folder, and the projects located within. *This is the default state for all project folders* * **Restricted:** Nobody except the users explicitly configured will have access to this folder. A member with access to a folder above it also gets in, unless you list that member here.

Once you select the restricted access, there will be a search bar where you can add users within your workspace. You can also select the role you want them to have. Press the "Save" button to have the changes go into effect.

{% hint style="info" %} To prevent lockouts, it's currently not possible to set permissions to a state where you won't be able to access the folder once the changes goes into effect. {% endhint %} ### What Restricted Access Blocks Members without access to a folder do not see the folder in the workspace, and the API folder list does not return its name or contents to them. They also cannot download dataset versions for projects inside the folder. This covers zip downloads, download links, and download tokens. Only members whose role can manage folder permissions see the "Set Permissions" option and the list of users who have access. ### How Access Applies to Subfolders Access to a folder also covers every folder inside it, at the same level, for members with no access set on the subfolder itself. If you give a member read and write access to a folder, they get read and write access to its subfolders too. Access set on the subfolder wins for that member, whether it is higher or lower than the parent's. If a parent folder is restricted, members with no access anywhere on that chain do not see the folders inside it, even ones set to "Anyone". A member granted access to the folder, or to a folder above it, still sees it. When a member has access to a subfolder but not to the folders above it, that subfolder appears at the top level of their project list. The names of the folders above it do not show up for them in the list, in the breadcrumbs, or in search. ### API Keys Scoped to a Folder An API key can be scoped to a folder. The key also reaches the folders inside that folder, but only the ones the member who created the key can access. If that member has no access to a nested folder, the key cannot reach the projects in it either. OAuth access tokens follow the same rule. ### Moving Projects and Workflows To move a project or a Workflow into or out of a folder, you need write access to that folder. A move between two folders needs write access to both of them. Some folder moves change who can see the folder. If you move a folder so it is no longer inside a restricted folder, your role must be able to manage folder permissions. The same rule applies when you delete a restricted folder, or a folder inside one, because its contents move up one level. This applies in the app and in the API.