​

Producer Access Request Guard & Appeal Flow

​

Summary

​

What’s New

​

Backstage Submission Guard

• Duplicate pending requests blocked — Users can no longer create a second request while one is already under review
• Revoked re-submission blocked — Users with revoked producer access cannot open a new request flow
• Global policy across request types — The guard applies across become-artist, verify-artist, and claim-artist
• Conflict error codes — Create attempts now return clear machine-readable conflict codes:
  • backstage_request_pending
  • backstage_request_revoked

​

New Submission Status Endpoint

• New endpoint: GET /api/v1/backstage-request/submission-status
• Returns a normalized eligibility payload:
  • can_submit
  • block_reason
  • message
  • contact_url
  • blocking_request_id
• Enables frontend pre-checks before a user starts a request

​

Revoked Appeal UX

• Revoked users get direct guidance — The request screen now shows an explicit appeal message and a clear Contact Support action
• Appeal path standardized — Users are directed to /contact for admin review and possible reinstatement
• Deep-link protection — Direct navigation to request forms is blocked when submission status is not eligible

​

Admin Revoke/Re-Approve Workflow

• Revoke action for approved requests — Admins can revoke producer access with notes
• User notification flow — Revocation sends the dedicated handled notification/email
• Re-approval support — Revoked requests can be approved again from admin tools when appropriate

​

Documentation & Developer Coverage

• Help docs updated — Producer Program application guidance now includes pending/revoked submission rules and appeal behavior
• Developer docs expanded — Content API and Error Catalog now document Backstage submission status, create conflict behavior, and revoke flow
• Audio Recon docs refreshed — Clarified current scan cadence and high-confidence match visibility details

​

Why It Matters

• Prevents request spam and duplicate records in producer onboarding workflows
• Gives revoked users a clear, controlled appeal channel instead of opening new requests
• Improves integration reliability with explicit conflict error codes and submission eligibility checks
• Keeps docs accurate for both end users and API consumers

​

Related

​

Feedback