Managing your media library
Registering assets with their rights and consent, organising them into folders, and what "ready" means when a post publishes.
Updated
The media library is your workspace's record of assets: what each one is, where it lives, who holds the rights to it and what its consent status is. Registering an asset records its details and a storage address - Social Studio does not upload the file for you, so the file has to already live at the address you give.
Consent that has expired is flagged in the list so an asset is not reused after permission has lapsed.
BEFORE YOU START
- A workspace you can reach. The library is per workspace.
- A publicly reachable address for each asset. The product stores the address, not the bytes.
- Nothing else. Registering, foldering and deleting assets cost no credits.
STEPS
- Open the workspace and choose Media, or go to /app/workspaces/{workspace}/media.
- Create folders under "Folders" if you want structure. Type a name and choose "Add folder".
- In "Register an asset", fill in "Name" and "URL", then pick a "Kind": image, video, audio, document or other.
- Choose a "Folder" and add "Tags" so it can be found later.
- Write "Alt text" for anything that will be published. This is the accessible description used when the asset goes out.
- Record the "Rights holder" and the "Consent status": unknown, granted, not required or expired.
- Choose "Register asset".
WHAT YOU SHOULD SEE
The asset in the table with its kind, folder, tags, rights and consent. Assets with no alt text carry a "no alt text" chip; assets whose consent has lapsed carry a "consent expired" chip.
WORTH KNOWING
There is no readiness screen in the library. An asset carries a status, and only an asset whose status is ready and which is reachable from the content's workspace can be attached to a publish. That check happens when a post publishes, not here, and it refuses with a named reason: the asset is inaccessible, the asset is not ready, or the network's own media rules reject it.
WHAT THIS WILL NOT DO
- It does not upload files. The bytes stay wherever the address points.
- It does not check rights or consent for you. Those fields record what you know; nothing verifies them.
- It does not attach media to a post. That is done from the content, and only images and videos can be attached, at most ten per item, with no duplicates.
- The mobile app registers a smaller record. It sends the name, kind, address and tags only; alt text, rights holder, consent status and folder are web-only fields.
- The list shows at most 200 assets.
IF IT DOES NOT WORK
- "Could not register {name}. Check the details and try again." usually means a missing name or address.
- "Could not create folder {name}." leaves the folder list unchanged.
- "Could not delete {name}." leaves the asset in place.
- "An attached asset is not available in this workspace." at publish time means the asset belongs somewhere you cannot reach from that content.
- "Only images and videos can be attached for publishing." means the kind is not publishable.
- "The same asset was attached more than once." means remove the duplicate.
- On mobile, "Could not load media." with a Retry button means the list failed, not that it is empty.
COMMON QUESTIONS
What does "consent expired" stop?
Nothing automatically. It is a flag so a person does not reuse an asset whose permission has lapsed.
Why does an asset have no alt text warning until I publish?
The chip appears in the library as soon as the field is empty. Publishing without it is what makes it a real problem.
RELATED GUIDES
- Generating an image
Pricing an image plan before anything is charged, choosing a model, and what happens when no image provider is active.
- Planning a video project
A video project is a plan made of scenes, captions and audio. Nothing listed there is a video file.
- Writing and approving content
The content editor - saving versions, submitting for approval, approving, and why an author cannot approve their own work.