> 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/announcements-and-updates/subuser-dashboard.md).

# Subuser Dashboard

Subusers with Dashboard access now get their own Zata.ai dashboard

\#Zata Subuser Dashboard

The **Subuser Dashboard** is now available.

Subusers created with **Programmatic + Dashboard access** get their own scaled-down version of the Zata.ai dashboard, scoped to only the buckets, regions, and permissions their account owner has granted them. They sign in at the same login page by switching the login mode to **Subuser**, using the credentials they set when accepting their invitation.

<figure><img src="https://2683631041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPPVG4W649TwXN8OejRhb%2Fuploads%2Fgit-blob-78c69cc01ecdd8a1143c9aa9b5d6cd9a801d6a3e%2Fsubuser_dashboard.png?alt=media" alt="Subuser Dashboard"><figcaption></figcaption></figure>

### What Subusers Get

| Section                     | What a subuser can do                                                                                                   |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Dashboard**               | Storage used, object count, accessible buckets and regions, region health for their own regions, and a buckets overview |
| **Buckets**                 | Browse the buckets shared with them, with search, region filter, and sorting                                            |
| **Media (Preview Manager)** | Preview images, videos, PDFs, and Office documents inline                                                               |
| **Access Keys**             | View their own access key and rotate it                                                                                 |
| **Policies**                | Review the access rules granted to them and request additional permissions                                              |

### Requesting Additional Permissions

Subusers can now ask for more access without going through a separate channel. From a rule's detail view in **Policies**, a subuser clicks **Request Policy** to request additional actions on a bucket. The account owner approves or rejects the request from their own Policies section, and the subuser sees the outcome under the **Requested** and **Rejected** tabs.

### What Stays with the Account Owner

The subuser dashboard deliberately excludes account-level controls. Subusers **cannot**:

* Create new buckets
* Create, deactivate, or delete access keys — rotating their own key is allowed, and the account owner is notified when it happens
* Access billing
* Invite or manage other subusers

Anything a subuser is missing — a bucket, a region, or a permission — has to be granted by the account owner from the main dashboard.

> **Note** Programmatic-only subusers are unaffected. They have no dashboard login and continue to use their access keys directly with S3-compatible tools.

### Getting Started

* [Subuser Dashboard](https://docs.zata.ai/subusers/subuser-portal) — a full walkthrough of every section
* [Create a Subuser](https://docs.zata.ai/subusers/create-a-subuser) — grant **Programmatic + Dashboard** access
* [Access Types & Bucket Permissions](https://docs.zata.ai/subusers/roles) — what each access type allows
* [Managing Invitations](https://docs.zata.ai/subusers/managing-invitations) — how a subuser activates their login