Object Storage dashboard
The Object Storage UI lives at Storage in your workspace sidebar. From there you can create buckets, manage workspace-wide access keys and drill into a single bucket for files, per-bucket keys and settings.
Storage list page
Section titled “Storage list page”The landing page lists every bucket in the workspace, with four aggregate stats across the top: total storage (bytes stored across all buckets), object count, bucket count, and the egress used so far this month.
Two actions live here. Create API Key issues a workspace-wide key with full or partial permissions across all buckets, covered in Access keys. New Bucket opens the bucket creation modal.
Create at least one access key first
You can browse and manage buckets in the dashboard without keys, but to upload from your code or CLI you need credentials. The UI nudges you to create a key before your first bucket.
Creating a bucket
Section titled “Creating a bucket”The New Bucket modal asks for two things:
| Field | Notes |
|---|---|
| Bucket Name | 3–63 characters. Lowercase letters, digits and hyphens only. Must start and end with a letter or digit. Unique within your workspace. |
| Public access | Toggle. If on, anyone with a direct URL can read objects without credentials. Off by default. |
After creation you land on the bucket detail page.
Bucket detail page
Section titled “Bucket detail page”Every bucket has four tabs.
Overview
Section titled “Overview”Top stat cards show Storage Used, Objects, Visibility (Public / Private) and Created date.
Below that sit two info panels. Bucket Info repeats the name, visibility, creation date, storage usage and object count. Connection Info gives the bucket name and the protocol (S3-compatible), which you pair with an access key to connect any S3 client.
A shortcut card jumps to Bucket API Keys (the Keys tab) so you can issue credentials scoped to this bucket only.
A full file browser. Drag and drop onto it to upload, or click to pick files; large ones switch to a multipart upload on their own. New folder creates a logical folder, which in S3 terms is just a key prefix ending in /. Click into folders to navigate and .. to go back up.
Each file has a download icon, and Share link copies a presigned URL that stays valid for a short period, or a permanent public URL if the bucket is public. Delete one file at a time, or multi-select and use Delete Selected.
The browser lists up to a few hundred objects per page and supports prefix-based navigation, so deep folder trees stay fast.
API keys scoped to this bucket only. Workspace-wide keys, created on the Storage list page, can already touch every bucket. These are for the opposite case: a third-party app, a CI job or a teammate who should only see one bucket.
The create modal for a per-bucket key offers two access levels:
| Mode | What it allows |
|---|---|
| Read-only | List and download objects from this bucket. |
| Read & Write | Upload, read and modify objects in this bucket. Cannot delete. |
When the key is created the dashboard shows the access key, secret key, the endpoint URL and a ready-to-paste boto3 snippet. Copy them all now: the secret is shown once and cannot be retrieved later.
Settings
Section titled “Settings”One toggle flips the bucket between public and private. Switching it to public makes every object already in the bucket readable anonymously, not just new ones.
The danger zone holds Delete Bucket, which requires the bucket to be empty first.
Bucket name rules
Section titled “Bucket name rules”The dashboard validates names live, but for reference:
- 3 to 63 characters
- Lowercase letters (
a–z), digits (0–9) and hyphens (-) - Must start and end with a letter or digit
- No consecutive hyphens, no spaces, no uppercase
Names are unique within your workspace rather than globally, so images in your workspace will not clash with images in someone else’s.