> For the complete documentation index, see [llms.txt](https://docs.hedge.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hedge.video/mimiq/workspaces/stornext-permissions.md).

# StorNext Permissions

Avid has strict expectations when it comes to permissions, which is not always obvious when working with SAN storage like StorNext. While there are multiple ways to skin this cat, here's a proven permissions model when using Stornext with Media Composer. 

## Folder Structure

In this folder structure example, the Project Folder is the folder you turn into a [Workspace](/mimiq/workspaces.md).

* SAN volume
  * Avid Folder
    * [Project Folder](/mimiq/workspaces.md)
      * Avid Projects
      * Avid MediaFiles

## Client Permissions

Set the `umask` settings of each computer to `002` so that the default permissions of a newly created file will be `775`, which means the `owner` and `group` will be able to edit.

## Server Permissions

| Folder          | Other ("others", "world") | Assigned Users |
| --------------- | ------------------------- | -------------- |
| SAN volume      | Read                      |                |
| Avid Folder     | No Access                 | Read           |
| Project Folder  | Read/Write\*              |                |
| Avid Projects   | Read/Write                |                |
| Avid MediaFiles | Read/Write                |                |

An alternative for the `Project Folder` permission is to set a group sticky bit on the group folder with `chmod g+s Project Folder` . This will cause all files and folders to have the same group id. That way, you don’t have to work with the `Other` permissions, and it will also open up the possibility to use StorNext’s quota system if required.

<sub>(Big thanks to Nathan Fleming for the help)</sub>


---

# 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://docs.hedge.video/mimiq/workspaces/stornext-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.