> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.zata.prathamchopde.site/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.zata.prathamchopde.site/_mcp/server.

# Bucket settings

The **Bucket Settings** page shows a bucket's details and holds the settings you can change after you create it.

To open it, go to **Buckets** and select the gear icon (**Bucket Settings**) in the bucket's row. Inside a bucket, the **Bucket Settings** button at the top does the same.

![The Bucket List with an arrow pointing at the gear icon in the Actions column](/_fern-img/91248d90569516641ad851a16f565e09fc286c8af001ac960aa70675856a0528.webp)

## What is on the page

The page has one section for each setting, in this order. Each section opens and closes when you select its title.

![The Bucket Settings page of a bucket with Object Lock, showing the sections Basic Information, Versioning Management, Object Lock, Lifecycle Rules, Bucket Tags, Security and Access, Access Control and Storage Management](/_fern-img/faee3fd832e27434b54284747ba1e875ae788bd55b006ef563d888d9132fc60a.webp)

| Section                                         | What you can do there                                                                                |
| ----------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| [Basic Information](#basic-information)         | See the name, region, size, number of objects, dates and tags                                        |
| [Versioning Management](#versioning-management) | Turn versioning on or off                                                                            |
| [Object Lock](#object-lock)                     | Set a default retention and lock existing versions. Shown only for buckets created with Object Lock. |
| [Lifecycle Rules](#lifecycle-rules)             | Delete old files, old versions and unfinished uploads automatically                                  |
| [Bucket Tags](#bucket-tags)                     | View and edit the bucket's tags                                                                      |
| [Security & Access](#security--access)          | Make the whole bucket public or private                                                              |
| [Access Control](#access-control)               | Choose who can list, read or upload to the bucket (ACL)                                              |
| [Storage Management](#storage-management)       | Limit the size and number of objects in the bucket                                                   |

> **Note**
>
> Sub-users see a smaller page: **Basic Information**, **Versioning Management** and **Access & Permissions**, which lists what they are allowed to do in the bucket. See [Sub-user portal: Buckets](/sub-users/portal/buckets).

## Basic Information

This section is read-only. It shows **Bucket Name**, **Region**, **Current Size**, **Total Objects**, **Created On**, **Last Modified**, **Encryption** and the bucket's **Tags**.

**Encryption** always shows **SSE-S3 (Default)**. There is nothing to set here, and Zata does not accept server-side encryption options from S3 tools.

![The Basic Information section with bucket name, region, size, object count, dates and a tag](/_fern-img/3f30ad523b8362adc15dedd8b65c09e6718bd9a6cc733f754760daee49dcd73d.webp)

## Versioning Management

With versioning on, Zata keeps the old version of a file each time you overwrite or delete it, so you can [restore it](/buckets/delete-and-restore-files). Old versions use storage until you delete them, for example with a [lifecycle rule](/buckets/lifecycle-rules).

Use the **Version Control** switch to turn versioning on or off. The status shows one of three states:

| Status                       | Meaning                                              |
| ---------------------------- | ---------------------------------------------------- |
| **Enabled** (Active)         | Every change creates a new version                   |
| **Turned Off** (Suspended)   | No new versions are made; existing versions are kept |
| **Disabled** (Never Enabled) | Versioning was never turned on                       |

Once versioning has been on, it can only be turned off, never fully removed. On a bucket with Object Lock, versioning cannot be turned off at all.

![Versioning Management showing the Enabled (Active) status, the Version Control switch turned on and the note that versioning can only be turned off](/_fern-img/ec3a9a47d8f04fa48cd5f196c801150b9d5c9b2efee4f259f06b45c7c47534d0.webp)

## Object Lock

This section appears only for buckets that were created with Object Lock turned on. You cannot add Object Lock to an existing bucket, and you cannot turn it off.

| Setting                       | What it does                                                                                                                                                                                                                                                 |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Default Retention**         | Locks every new upload for a number of days, in **Governance** or **Compliance** mode. Choose the mode and the days, then select **Apply Changes** and type `CONFIRM`. **Remove Rule** stops locking new uploads; files that are already locked stay locked. |
| **Protect Existing Versions** | The default rule only covers new uploads. Select **Apply Retention…** to lock the versions that are already in the bucket and have no lock yet.                                                                                                              |

For the step-by-step guide, see [Set a default retention](/buckets/object-lock/overview#set-a-default-retention) and [Lock existing versions](/buckets/object-lock/overview#lock-existing-versions). To learn how the modes differ, see [Object Lock](/buckets/object-lock/overview).

## Lifecycle Rules

Lifecycle rules delete files for you on a schedule: files older than a number of days, old versions, and unfinished uploads. Use them to keep storage, and your bill, under control.

On a bucket with Object Lock, rules skip locked versions until their lock ends.

To add, edit or delete a rule, see [Lifecycle rules](/buckets/lifecycle-rules).

## Bucket Tags

This section shows how many tags the bucket has and lists them. Select **Edit tags** to add, change or remove tags.

For the tag rules (key length, allowed characters, at most 10 tags), see [Tags](/buckets/tags).

## Security & Access

This section has one switch, **Public Access**. Turning it on makes the whole bucket public: anyone on the internet can list all its files and download any of them without signing in. The console writes the bucket policy for you, so you don't need to write JSON.

For the steps, the public link format and what to check first, see [Make the whole bucket public](/buckets/make-a-file-public#make-the-whole-bucket-public). To share only one file, see [Make one file public](/buckets/make-a-file-public#make-one-file-public).

## Access Control

**Access Control** sets the bucket's ACL: who can list the files in the bucket and who can upload to it. You can choose **Private** (only you), **Public read**, **Public read + write**, **Authenticated User** (any signed-in Zata user) or **Authenticated User read + write**. Settings that open the bucket to others ask you to confirm first.

This is separate from **Security & Access**: that section writes a bucket policy, while this one sets an ACL. To learn what each setting allows and which one to use, see [Bucket ACL](/access/bucket-acl) and [Access control](/access/access-control).

## Storage Management

A bucket quota caps how much data and how many objects a bucket can hold. Uploads that would go over a limit are refused.

#### Open the quota form

Open **Storage Management** and select **Configure** next to **Bucket Quota**.

#### Set the limits

Turn on **Enable Quota**, then fill in one or both fields:

* **Storage Limit (GB)**: the most data the bucket may hold. It cannot be higher than your plan's storage (1 TB on a trial). Leave it empty to use your plan's limit.
* **Object Limit**: the most objects the bucket may hold. Leave it empty for no limit.

#### Save

Select **Save Changes**.

![The Bucket Quota form with Enable Quota on and the Storage Limit and Object Limit fields](/_fern-img/4d4435f54f41cce0152c44e0a616284e8e32a01912508964ba02f3860025406b.webp)

To remove the limits, turn off **Enable Quota** and select **Save Changes**.