Approval workflow
From “this one.” to APPROVED.
Approve or request changes on a named version. Each decision records who made it, when, and the checksum of the exact file, then moves the song to its next stage.
Artist ✓ Management ✓ Label ✓
- IDEA
- DEMO
- PRODUCTION
- RECORDING
- MIXING
- MIX REVIEW
- APPROVED MIX
- MASTERING
- MASTER REVIEW
- FINAL MASTER
- RELEASE READY
- RELEASED
- Harris J Artist15:10
- Karim Management15:42
- Nadia Label17:05
SHA-256 4c1e…90ab · Mix 20 · Hayati Mix 20.wav
How it works
- 01A new version arrives and the people who approve are notified.
- 02Each listens, A/B’s against the previous mix if they want, and chooses Approve or Request changes.
- 03Request changes with a note; the engineer sees it with the timestamped comments.
- 04When it’s approved, the song moves to the next stage, and the master can later be marked as the Official Master.
- EXACT FILE
Approved means this file
Every approval stores the SHA-256 of the version approved. A re-export is a different file, and it shows.
- NAMED
Who and when
“Hayati · Mix 20 approved by Karim.” Never an anonymous status change.
- WORKFLOW
Stages that move
Idea through mix review, approved mix, mastering, final master, release ready and released. Workspaces can add their own.
- PERMISSION
Only approvers approve
Approving is a permission: managers, admins and owners by default.
- AUDITED
On the record
Approvals and change requests are written to the audit history with the checksum.
- INBOX
Asked, not chased
People see what’s waiting for their approval without a message thread.
Questions
Can more than one person approve?
Yes. Each approver’s decision is recorded separately against the same version, so you can see artist, management and label sign-off side by side.
What happens after approval?
The song’s workflow status advances automatically, and the approved version is marked APPROVED in every list.
One home for every song.
Versions. Feedback. Masters. Your studio. Your cloud. Your team.