> For the complete documentation index, see [llms.txt](https://docs.zata.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zata.ai/subusers/create-a-subuser.md).

# Create a Subuser

**Step 1: Open the Sub-user Management**

{% hint style="info" %}
You can create only three SubUsers.
{% endhint %}

* Log in to the Zata.ai dashboard.
* From the left sidebar, go to **Subusers → Subusers**
* You will see the **Sub-user Management** page

<figure><img src="/files/cqTpaDCi2iB7cvqLsAd6" alt=""><figcaption></figcaption></figure>

**Step 2: Create a New Subuser**

* Click on **Create Subuser** (top right button)

  A popup will open: **Create Subuser**

**Required Fields**

* Username:
  * Must be unique
  * Allowed characters:
    * Letters (a–z, A–Z)
    * Numbers (0–9)
    * Dot (.)
    * Underscore (\_)
    * Dash (-)
  * Length: **1–64 characters**
* Email:
  * Enter a valid email address
* Region:
  * Select the required region from dropdown(indore)

**Optional Field**

* Description
  * Add any note (optional)

<figure><img src="/files/9i00Nwqg97ulA8Me6PPE" alt=""><figcaption></figcaption></figure>

**Step 3: Create the Sub-user**

* Click on **Create Subuser**

After clicking:

* Sub-user is created successfully
* A **credentials file is automatically downloaded**

Important Note:

* This file contains:
  * Access Key
  * Secret Key
* You **cannot retrieve the Secret Key again later.**

**Step 4: Save Credentials Securely**

* Downloaded file must be stored securely
* If lost:

  * You need to **generate a new key**
  * Old key must be deleted.

**Step 5: Verify Sub-user Creation**

After creation, you will see the sub-user listed with:

* Username
* Assigned Buckets
* Status (**Active**)
* Last Active
* Actions

Status should be **Active** but Initially, no bucket is assigned

<figure><img src="/files/n8rvbPYRy8yVNzfhSCq4" alt=""><figcaption></figcaption></figure>

**Step 6: Open Sub-user Details**

* Click on the **Sub-user name**

&#x20;You will open **Bucket Access Management page**

**Step 7: Assign Bucket**

* Click on **+ Assign New Bucket**

You will proceed to assign access to a bucket

<figure><img src="/files/meaQTEHCtouTPyWcADSM" alt=""><figcaption></figcaption></figure>

**Step 8: Configure Access Rule**

A popup will appear: **Add Access Rule**

Select permission:

| Permission    | Description      |
| ------------- | ---------------- |
| View Only     | Read access      |
| Upload Only   | Upload only      |
| View & Upload | Read + Write     |
| Full Access   | Complete control |

For testing, select **Full Access**

* Click **Create Rule**

<figure><img src="/files/9ZjEsRwUbPOs9pg9oh6W" alt=""><figcaption></figcaption></figure>

**Step 9: Verify Access Rule**

You will be redirected to **Manage Bucket Access Rules page**

Check:

* Permission → Full Access
* Status → Active

&#x20;This confirms access is successfully configured

<figure><img src="/files/R1Ip2IVePQMrLbYg7bfs" alt=""><figcaption></figcaption></figure>

**Step 10: Final Verification**

Go back to **Sub-user Management page.**

Check:

* Assigned Buckets : 1
* Status :  Active

Sub-user is now ready to use

<figure><img src="/files/yTLJ0yn0P4mt9eMlftyo" alt=""><figcaption></figcaption></figure>

Sub-user creation and access configuration is successfully completed.\
The user can now access assigned buckets using S3-compatible tools.

<figure><img src="/files/Wpw1IPphZOSlDjQLuqbu" alt=""><figcaption></figcaption></figure>


---

# 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.zata.ai/subusers/create-a-subuser.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.
