Published vs. available content on alugha

Summary

alugha projects have a three-state publish model — published, available, and not created — combined with language-level STATE (Playable / Private / Hidden) and a project-level STATE (Public / Unlisted / Private). Understanding how these layers interact is the difference between “I hit Publish All and it should be live” and “my viewers can actually see the video.”

Three layers of visibility

alugha separates “is this content ready?” from “should viewers see it?” across three independent layers:

Track state (published / available / not created) — per-language, per-asset. Audio and subtitles each have their own state on each language.
Language STATE (Playable / Private / Hidden) — per-language. Controls whether the language shows up in the player at all.
Project STATE (Public / Unlisted / Private) — whole project. Gates the entire video.

A language is visible to viewers only when all three layers say yes: the project is reachable, the language is Playable, and the track is published.

Track state — the three-state model

On the dubbr’s PROJECT tab, every language row shows the state of each asset (AUDIO, SUBTITLES, CC).

published

The track is live to viewers. The alugha player serves it. Embeds and shared links see it. Teal badge.

available

The track is finished and correct, but not yet live. You can preview it in the dubbr, but viewers outside don’t see it until you publish. Teal badge.

Click Publish All on the PROJECT tab to move every available track to published in one go — see Publish your multilingual video project.

not created

The track doesn’t exist yet. Most commonly: closed captions for a language where you haven’t run Copy Dub To Subs, or a language you just added where the AI pipeline hasn’t been triggered. Grey badge.

Create it first (run Speech-To-Text, Translation, Text-To-Speech, Import Subtitles, or Copy Dub To Subs) — it will flip to available, and you can publish it from there.

Language STATE — Playable, Private, Hidden

Separate from the track-state model, every language has a STATE set on its language tab (see Edit title, description, tags, and thumbnails for each language).

alugha language-level STATE dropdown with Playable, Private, and Hidden options showing on a dark dubbr panel to understand published vs available content

Playable — the language shows up in the player’s language picker. Default for newly created languages that are ready.
Private — the language exists on the project but is hidden from viewers. Useful for work-in-progress or unreleased languages.
Hidden — the language is invisible in listings but still reachable by direct link. Useful for staging or stakeholder previews.

Language STATE overrides track state. A language with Private STATE won’t appear in the player even if every track is published.

Project STATE — Public, Unlisted, Private

At the top level, the whole project has a STATE too — see Set video visibility and privacy.

Public — searchable, embeddable, share-link works for anyone.
Unlisted (sometimes shown as Not listed) — not searchable, but accessible to anyone with the link.
Private — only you and your collaborators can access it.

Project STATE is the outermost gate. If the project is Private, no viewer sees any language regardless of how many tracks are published or how many languages are Playable.

How the layers combine

Think of the three layers as AND gates. A viewer sees a language’s audio or subtitles only if:

Project STATE lets the viewer reach the project at all (Public, or Unlisted with the link, or Private with collaborator access).
Language STATE is Playable (or Hidden if the viewer has the direct link).
Track state is published for the asset in question (audio or subtitles).

All three must be green. The easiest way to debug a “why can’t they see it?” problem is to walk these three gates from the outside in.

Common scenarios

Ship one language first, polish the others later:

Publish only the primary-language tracks (set to published).
Leave other languages’ tracks as available and their language STATE as Private until you’re ready.
Flip each language to Playable as it’s finalized — no re-publish needed if the tracks are already published.

Preview with a stakeholder:

Keep the project Unlisted (not searchable).
Set the reviewer-facing language to Playable and publish its tracks.
Share the link. After sign-off, flip the project to Public to launch.

Take a language down temporarily:

Change that language’s STATE to Private. The tracks stay published, but the language drops out of the player.
Other languages are unaffected.
Flip back to Playable when ready.

Good to know

Track states (published / available / not created) apply to assets (audio, subtitles, CC) — not to the language as a whole.
Language STATE (Playable / Private / Hidden) applies to the whole language and overrides the track-state layer.
Project STATE (Public / Unlisted / Private) applies to the entire project and overrides everything below it.
The alugha player falls back to the default language if the viewer’s browser language isn’t available — make sure your default is published and Playable.
Changes are usually live within seconds, but CDN caching can delay visibility for a minute or two on embeds.

Was this article helpful?

Understand published vs. available content