Client projects, clear reviews and approved deliveries
Start projects from a template, collect the missing files, compare revisions and hand over the exact work your client approved.
Media Studio 0.3 brings six client project tools together in one update and one source download. It helps an agency follow a project from the first requested logo to the approved delivery. These screenshots show the real app with fictional Cedar Plumbing and Juniper Florist examples.
- Start client projects from reusable empty folder structures and file checklists.
- Collect requested files with due dates, upload-only links and clear received or not-needed statuses.
- Review selected file versions together and record one complete approval or change request.
- Compare two saved versions in side-by-side read-only previews.
- Download approved handover ZIPs with the exact reviewed files and their decision manifest.
- See missing files, pending rounds, stored versions and expiring links across client projects.
Start the next client project with a familiar structure
Open Client projects → Project templates and save your folder names and requested-file labels. Use the template to create a new project with its own client name and due date.
Templates start empty. They do not bring across another client’s files, feedback or sharing links. New folders inherit their destination’s existing staff access; check that access before adding private work.
Know which files are still missing
File collection gives each requested item a due date and a clear received, missing or not-needed status. Choose a file already in the project to mark it received, or create an upload-only request link.
Edit the label or deadline as plans change. If a requested item is no longer needed, record a short explanation; its client upload link pauses until you require it again. Received means a file arrived, so you can still review whether it is the right one.
Give the client a simple place to send the file
The client opens the requested item’s page, sees what you need and its deadline, then uploads the file. The page does not let them browse your existing project files or replace an earlier version.
Existing password, recipient verification, expiry and request limits still apply. Local testing shows a verification code without sending email; hosted recipient verification uses your configured sender.
Check the new version beside the original
Open a file with more than one saved version and choose Compare versions. Pick the earlier and later versions to view their read-only previews beside each other.
This is a visual comparison you make yourself. It does not automatically highlight changes. Office previews show text or cached cells, and media playback depends on browser codecs. Original downloads retain the original file.
Review the selected files as one complete round
In Approval rounds, select the file versions, write a short summary and save a private round. Inspect it, then publish a client link when it is ready.
The round keeps the versions you selected. Later uploads do not change what is under review or inherit its approval. A revised delivery needs a new round. You can select up to 100 files and 200 MiB together.
Keep the client’s decision with the reviewed work
The client reads the selected files and approves the complete round or requests changes with a note. Approval asks them to confirm they reviewed every selected version. The decision stays with that round.
Link-only names record who the link holder says they are. Recipient-only links verify an allowed email separately. You can protect, replace or withdraw the link using the existing sharing controls.
Hand over the approved files in one ZIP
Approval unlocks a handover ZIP with the exact reviewed files and a small manifest recording the versions and decision. Download it from the client page or from Handovers in your workspace. Internal notes and unrelated drafts are left out.
Keep the selected original files in their client project. Moving, restricting or trashing one withholds the public round. Permanent deletion requires withdrawing the rounds that use it. Withdrawing access cannot recall copies already downloaded, and purging originals removes their future handover availability.
See what needs attention across clients
Overview brings together missing and overdue files, pending and overdue rounds, stored version bytes and links expiring in the next seven days. It shows up to 50 accessible projects and tells you when the list is limited.
Storage includes version history and trash. Due dates help you plan follow-up; they do not automatically send reminder emails. Client decisions refresh in the project workspace while it is open.
Try it in your own workspace.
- Download Media Studio 0.3 from your portal library. It is one source ZIP, included with DevLaunch All Access.
- For a new installation, read START_HERE.md and INSTALL.md. For an existing copy, follow UPGRADE_0_3.md: verify a backup, preserve private configuration and signing keys, check customizations and review the source merge before updating.
- Keep the included lockfile, install dependencies, apply the pending migration and restart. Verify your existing files, versions, comments and protected links. Existing folders are not automatically converted into client projects.
- Open Client projects and try one small fictional project: collect a file, save a private review round, request a revision and download the approved handover.