Media Storage
ADMINISTRATOR
Media storage holds the visual assets used in published content. Its configuration determines whether an asset is publishable.
Media storage configuration. States and counts shown are point-in-time examples.
What matters operationally
- Tenant-scoped storage — assets are held within the tenant boundary, not in a shared pool.
- Object ownership — every object is owned by a workspace, and ownership is enforced at publication time.
- Asset verification — an object must be verified before the asset it backs can be published.
- Lifecycle state — pending, active, or retired.
- Cutover readiness — whether the workspace is ready to move fully to active storage.
- Legacy read-only versus active storage — legacy objects can be read and referenced historically but are not the target for new writes.
Do not publish storage credentials, secret references, signed URLs, or internal object keys anywhere — in documentation, in story content, or in asset descriptions.
Checks before publication
- The asset resolves and is verified.
- The object is owned by the publishing workspace.
- The object is in active storage, or a deliberate legacy reference is acceptable for that post.
- No storage warning or conflict is outstanding for the workspace.
A storage warning is a publication risk, not a cosmetic issue: an unverified or mis-owned object is refused before send.
Was this helpful?
Last updated 1 month ago