Account
Loading account...
Admin Center
Permission-gated operations across The Dub Factory. Operating Unit workflows and shared platform services are organized here before functional integrations are connected.
Loading Admin Center mode...
Loading account...
Loading roles...
Planned consolidated view of assigned work, watched records, pending reviews, and owned follow-ups across Operating Units and shared platform services.
Planned exception surface for blocked work, failed integrations, delivery problems, billing attention, access issues, and workflow risk.
Planned activity stream showing meaningful operational changes, system events, assignments, approvals, and delivery milestones.
Planned status snapshot for Studios, Media, Technology, and 16-bit Records without duplicating shared platform services inside each unit.
Planned read-only summary of backend, database, authentication, email, payments, files, integrations, and staging/production environment state.
Read-only Admin Center shell. Data-writing operational actions are intentionally not wired in this version.
Read-only production visibility through the Platform Portal permission model.
Active custom song production queue. Focus on what is next.
Select a Studios service to load its workflow and active Work Orders.
Customer source material and processing requirements appear here.
Processing expectation for this Work Order.
Customer-visible final files should be marked as deliverables before completion.
Source material, working files, revisions, and customer deliverables attached to this Work Order.
| Role | File | Visibility | Size | Uploaded | |
|---|---|---|---|---|---|
| No files loaded. | |||||
Loading production record...
Review the immutable customer source, assign the work order, verify intake, and request customer clarification only when needed.
Choose the accountable Studios owner. Only active Portal members with Studios access are eligible.
Confirm that the captured customer information is complete enough to move into lyrics preparation.
Shape verified Story DNA into a controlled creative brief, generate lyrics deliberately, refine selected sections, and manage the customer lyrics approval loop.
Turn the verified customer story into a focused lyrics brief, refine it if needed, then generate an original lyrics draft.
Combine customer musical direction with controlled production choices. Untouched controls remain customer-led and AI-inferred; explicit staff selections become hard overrides.
This is one of the four primary song-generation inputs. Generate or edit the Suno-ready style directly, or open Style Properties to control the musical decisions used to rebuild it.
Upload the finished song, review delivery readiness, prepare the customer completion message, and complete the Work Order from one controlled workspace.
Attach the final customer-ready master. MP3, WAV, or M4A files are accepted up to 100 MB. Uploading a replacement file updates the delivery artifact while preserving the Work Order history.
This delivery uses the standard Dub Factory Studios completion template. Template management will move to Communications in a later rollout.
Label operations for artists, releases, masters, agreements, ownership, distribution, and royalties.
Artist profiles, participation, contacts, relationships, and label context.
Release planning, status, dates, track lists, artwork, and launch coordination.
Authoritative master recordings, versions, assets, and ownership references.
Agreements, ownership splits, rights context, and participation records.
Distribution partners, delivery status, identifiers, territories, and release handoff.
Statement intake, reconciliation, allocations, and reporting foundations.
Media-oriented client work, creative production, campaigns, deliverables, assets, and approvals.
Media-owned project portfolio and lifecycle visibility.
Briefs, requests, intake, requirements, and creative direction.
Campaign planning, schedules, channels, assets, and outcomes.
Production outputs, review state, due dates, handoff, and completion.
Reusable creative assets tied into shared project-file infrastructure.
Client and internal approval queues with history and accountability.
Technology Work Orders with the technical details tucked inside the work, not scattered across separate menus.
1 layout-preview Work Order shown. No Technology backend records have been created.
Canonical human identity, Membership, organizational placement, Application access, Roles, and access review.
Create one platform identity, then explicitly choose Application access and Roles. When Portal access is selected, the administrator issues a 24-hour temporary password that must be replaced at first sign-in before MFA.
This password is shown once. Copy it now. The user must replace it at first sign-in.
| Account | Status | Email Verified | Memberships | Created |
|---|---|---|---|---|
| Loading Accounts... | ||||
Loading Account relationships...
Password setup/reset and email verification links are emailed directly to the Account address, are single-use, and expire automatically.
Review active Membership, Application access, Roles, stale assignments, expirations, and revocations.
Deliberately coordinated engagements. Standalone Work Orders stay in their Operating Unit queues until staff or an automated multi-service workflow groups them here.
Create the commercial engagement first. Operating Unit Work Orders are added after the Project exists.
Proposal, negotiated pricing, executed agreement, deposit requirements, and activation controls will connect in the following slices.
Choose an existing standalone Work Order. It will keep its Operating Unit and customer attribution while becoming part of this Project.
Proposal estimates, negotiated pricing, agreement status, deposit requirements, and Project activation.
Internal execution, dependencies, milestones, handoffs, and customer-required actions beneath Work Orders.
Organization-owned reusable Roles mapped to the platform-owned Permission catalog. Direct Permission grants to Accounts or Memberships are intentionally prohibited.
Use this when the established Roles do not match the Permission bundle you need. The new Role becomes assignable during Account creation and access management.
Generate repeatable staging scenarios against the real Studios and Technology Work Order models using controlled customer identities.
Technology Regression Library
Loading the reusable scenario catalog...
Scenario Harness
Choose an Operating Unit, Work Order family, and whether the scenario should be standalone or Project-associated. Nothing is written until you create the reviewed scenario.
Checking the four persistent staging customer identities...
Read-only visibility into recorded customer messages and delivery notifications already persisted by Studios workflows.
Loading communication record...
Future operational message composition, audience controls, context, and history.
Future shared templates with business- and application-specific branded variants.
Future unified visibility for authentication, verification, payment, workflow, and system-generated communications.
Shared operational handoff from billable Work Order activity into Finance. Queueing does not advance lifecycle stage.
Invoice creation and receivables remain a separate financial operation after queue review.
Actual money movement, receipts, refunds, and provider reconciliation.
Read-only operational visibility into existing Studios delivery records. This slice does not create a generalized file repository or expose direct download URLs.
| Work Order | Customer | Package | Status | Artifact | Uploaded | Expires | Delivered |
|---|---|---|---|---|---|---|---|
| Delivery records have not been loaded yet. | |||||||
Loading delivery record...
Future shared logical file records, categories, visibility, and deliverable state.
Future immutable binary versions, checksums, scan state, and supersession.
Future pending, failed, quarantined, and completed upload visibility.
Future storage-provider health, retention classes, archival, and deletion lifecycle.
Cross-platform operational, financial, service, security, audit, and compliance reporting foundations.
Work status, lifecycle, throughput, backlog, delivery state, assignments, and exception trends across Operating Units.
Revenue, obligations, payments, expenses, balances, margin, and project profitability.
Capacity, queues, assigned work, overdue work, internal bottlenecks, and participant workload visibility.
Change history, access reviews, sensitive actions, administrative operations, and evidence exports.
Read-only operational evidence from the governed migration-control subsystem. No migration, validation, reconciliation, rollback, SQL, or maintenance actions are exposed here.
| Run | Command | Status | Pending | Applied | Failed | Started |
|---|---|---|---|---|---|---|
| Migration runs have not been loaded yet. | ||||||
| Run | Suite | Work Package | Status | Passed | Failed | Errors | Started |
|---|---|---|---|---|---|---|---|
| Validation runs have not been loaded yet. | |||||||
| Event | Action | Actor | Object | Occurred |
|---|---|---|---|---|
| Audit events have not been loaded yet. | ||||
Loading run evidence...
Future service-health visibility across backend, database, email, payments, storage, authentication, and dependencies.
Future cross-platform administrative and security event visibility beyond migration-control evidence.
Future provider status for Stripe, Microsoft Graph, OpenAI, storage/SFTP, and other dependencies.
Remains isolated from this read-only surface and is not exposed as an action here.