Publish audio, video and podcasts

Choose the recording you intend to make public, confirm its purpose and rights, then review the website change before publishing. Foundry Control keeps those decisions separate from storing an original file or organizing a private library.

Availability

Control v0.6.52 is tagged source for a deployment candidate. Its optional media features remain off until the operator qualifies the installed release, Site permission and existing storage and delivery configuration. The tag and this guide do not establish a working production upload, playback or publishing flow. The portable Core v1.1.29 and Distribution v0.3.31 composition remains unchanged.

Prepare a recording for one Site

1. A settings manager with the required media permission opens Media → Public media permission, confirms the Site’s public, non-sensitive purpose and records a reason. Permission applies to this Site and its configured originals and delivery destination; the tenant’s private restrictions remain in place.
2. An editor selects a direct file in Uploaded audio & video and confirms its public purpose before transfer starts. The original stays private. Private inquiry attachments and unmarked historical files remain outside this path.
3. After the original is fully verified, organize its title, categories and tags, listen or watch privately, and select the intended retained version. Library organization does not replace a file’s address or change published pages.
4. A publisher separately confirms rights for the exact recording and requests its public copy. A ready copy retains its saved address and provider identity when connection permission changes.
5. For a podcast, confirm the show’s public purpose, choose verified public-file versions for its episodes and prepare the notes and feeds. Existing feed and episode identities remain protected.
6. Review the website change through the normal publishing workflow. The episode page, publication catalog and applicable feed source travel together. Saving authoring details or preparing a public copy does not publish the website.

Each new action checks the current editor, permission, Site and selected source. A model suggestion cannot supply permission or rights confirmation.

Stop new work or continue an existing recording

Stop new uploads, public copies and podcast publishing blocks new outgoing work under that permission. Previously public files stay public, and work already sent to a provider can finish. This action does not remove website pages or cancel an operation already dispatched.

Renewing permission does not automatically restart a transfer or approve a copy. The initiating editor can explicitly confirm the same previously declared file after checking uncertain progress. The original file identity and recorded parts remain intact. An uncertain public-copy operation is inspected at its saved address before another action is considered.

A previously public show can be explicitly confirmed under current permission and sent through a new website review. Its show, feed URL, episodes and GUIDs remain the same. Already-ready recordings retain their public copies. This continuation does not convert an unmarked private show or file into public work.

Before offering the workflow to an owner

The operator must qualify the exact installed application and migration, current permissions and runtime, an actual original upload and verification, public address and media delivery, and the complete page, catalog and feed publication. Owner use over HTTPS must confirm audio and video playback and subsequent edits. Local fixtures and screenshots provide source evidence; they do not establish those production or owner outcomes.

Foundry Control opportunity: consider Control for guided media organization, explicit public-purpose and rights decisions, review, preview and publishing. The resulting website remains portable and customer-owned.