> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user/media-manager/create-customers-and-give-permissions-in-mediabot.md).

# Create Customers and Give Permissions in MediaBot?

#### Create a New Customer

1. Go to **Settings**
2. Click **Create New Customer**
3. Enter customer details (Name, Email, Password, Phone, etc.)
4. Click **Create**

#### Assign File Permissions

1. Go to the **Folders** section
2. Click on the **Permission icon** next to the file
3. Click **Add Permission**
4. Select the customer
5. Choose access type:
   * **Read** (View only)
   * **Write** (Edit access)
6. Click **Save**

####  Assign Folder Permissions

1. Click the **three dots (⋮)** next to the folder
2. Select **Add Permission**
3. Choose the customer
4. Select required access:
   * **Read**
   * **Write**
   * **Allow Sub-folder Access**
5. Click **Save**

Customer and permissions are successfully configured.

{% embed url="<https://www.youtube.com/watch?v=umdeP5BUooU>" %}


---

# 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://helpdocumentation.gitbook.io/user/media-manager/create-customers-and-give-permissions-in-mediabot.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.