> ## Documentation Index
> Fetch the complete documentation index at: https://docs.up.telestream.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Storage

> Register and manage the storage locations Telestream UP reads and writes media to

## Overview

The Storage settings page lets admins register the external storage locations — S3-compatible buckets — that Telestream UP applications use to store and read media. Go to **Settings → Storage**.

This page is admin-only / entitlement-gated: you'll only see the **Storage** tab if your role or organization plan grants access.

## Viewing storage locations

The table lists every registered store: name, bucket (or share) name, permission level (**Read**, **Read and Write**, or **Read, Write, and Delete**), region, and type. Use the search box to filter by name, and click a column header to sort.

Stores that have sub-storages (named sub-paths inside a store, useful for organizing content) show an expand arrow — click it, or double-click the row, to reveal them.

## Adding a storage location

Click **Add Storage**, pick a **Storage Type** (the list only shows types your deployment supports), and fill in the type-specific fields:

| Type                      | Key fields                                                                                                                                                                                                                       |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| AWS S3                    | Choose **Use AWS IAM Role** (Role ARN, with a read-only External ID and Account ID for setting up trust) or **Use access key and secret key** (Access Key, Secret Key); plus Store Name, Region, Bucket Name, Storage Permission |
| Generic S3 / Backblaze S3 | Endpoint, Access Key, Secret Key, Store Name, Region, Bucket Name, Storage Permission                                                                                                                                            |

Store names must be 3–63 characters (letters, numbers, spaces, underscores, or hyphens, starting and ending with a letter or number). Once created, a store's **type** and **name** can no longer be changed.

Click **Add** to finish. A confirmation toast appears once the store is added, or an error naming the store if it fails.

for Guidance on how to create the needed Roles for AWS S3, see ....(LINK)

## Editing and checking a store

Select a store and choose **Edit** to update its connection details (type and name stay locked). Choose **Check Permissions** to have the platform verify the stored credentials actually work — you'll see a toast confirming success or explaining the failure.

## Adding a sub-storage

Select a store and choose **Add Sub Storage** to create a named path inside it — give it a **Sub Storage Name** and a **Path** (must end with `/`). Sub-storages appear nested under their parent store and can be edited or deleted independently.

## Deleting

Select one or more stores (checkboxes support multi-select) and choose **Delete**. You'll be asked to confirm — deleting is permanent. Deleting a sub-storage similarly asks you to confirm, and explicitly notes that removing it won't affect the parent store.

## When there's nothing here yet

If no storage locations are registered, the page shows "No Stores Have Been Added" with an inline **Add** link to get started.