> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/help-center/drive-faq/file-folder-permissions.md).

# File and folder permissions

Workspace admin or drive managers can manage who can be invited to certain workspaces and drives, and determine their inheritance in the management structure.

A drive manager is a workspace member or workspace admin that actively manages who can be invited to this drive and what permissions are inherited from the workspace.

Here are the permission settings that can be assigned.

* Full Access - Able to create shareable links and shareable modifications on files and folders and the actions below.

  NOTE: Full access is not equivalent to being a drive manager.
* Editor - Able to edit and move files and folders around within the drive
* Commenter - Able to comment and approve of files
* Viewer - Able to view files but not comment


---

# 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://academy.shade.inc/help-center/drive-faq/file-folder-permissions.md?ask=<question>&goal=<user_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.
