How to Set Up Platform Team Access Before a Release Campaign
A practical access checklist for Spotify for Artists, Apple Music for Artists, YouTube Studio, distributors, ad accounts, and release-campaign handoffs.
The short answer
Set up platform team access before a release campaign by giving each operator the minimum role they need on Spotify for Artists, Apple Music for Artists, YouTube Studio, distributor dashboards, smartlinks, and ad tools. Avoid shared passwords. Assign owners, document recovery contacts, confirm two-factor access, and remove temporary users after the campaign review.
Three things to know
- 01
Platform access is a release-readiness task, not an admin detail to solve after launch week starts.
- 02
Use named team roles, two-factor recovery, and least-privilege permissions instead of shared passwords.
- 03
A clean handoff helps labels, managers, and contractors move faster without taking more control than the campaign requires.
Platform access handoff checklist
Use this before a manager, label, contractor, or label-services team starts campaign work.
- 01
Role map
List who needs profile editing, uploads, analytics, ads, links, reporting, or approval access.
- 02
Admin owner
Confirm one artist-side owner can invite users, remove users, reset access, and approve risky changes.
- 03
Platform check
Test Spotify, Apple Music, YouTube, distributor, smartlink, social, ad, and email access before launch week.
- 04
Scope boundary
Write down which partner actions are allowed, which need approval, and which accounts stay read-only.
- 05
Offboarding date
Set the date when temporary users are removed and final campaign reports are archived.
What access should be ready before campaign planning starts?
The team should confirm access to Spotify for Artists, Apple Music for Artists, YouTube Studio, the distributor dashboard, release landing pages, ad accounts, social accounts, email tools, asset folders, and reporting sheets. Not every person needs every login. The practical goal is simple: anyone responsible for pitching, profile updates, video publishing, ads, or reporting can do the work before the release clock gets tight.
Why should artists avoid sharing passwords?
Shared passwords create confusion when a campaign gets busy. The team cannot tell who changed a bio, moved a date, edited a link, or downloaded a report. They also make offboarding harder after a one-release engagement. Named users and platform roles create a cleaner record of responsibility. If a partner only needs analytics, do not give them the same access as someone who can publish or change account settings.
How should Spotify for Artists access be handled?
Spotify for Artists supports artist-team access, so the campaign owner should confirm who has admin access, who can invite the release operator, and what role fits the work. A playlist pitch, Canvas upload, Clip, Artist Pick, profile update, Countdown Page check, merch update, or reporting pull may require access before release day. Add the person early enough to test the workflow before delivery deadlines arrive.
How should Apple Music and YouTube access be handled?
Apple Music for Artists and YouTube Studio should be checked before the campaign depends on them. Apple access may matter for profile management, Promote assets, pre-add review, milestones, and reporting. YouTube access may matter for uploads, Premieres, Shorts, Community posts, analytics, permissions, and channel safety. If a channel is managed by a collaborator, video team, or old manager, solve that before announcing a video schedule.
What should a label-services team receive?
A label-services team usually needs campaign inputs, not open-ended control. Provide the release date, ISRCs, UPC if available, final artwork, master links, distributor status, profile links, smartlink admin or reports, ad-account access if ads are included, social posting plan, and platform analytics access. The agreement or scope should say which systems the partner can edit, which are read-only, and who approves changes.
How should access be removed after the campaign?
Schedule offboarding when the post-release report is finished. Remove temporary users, rotate any shared passwords that had to be used, archive exported reports, confirm who keeps smartlink and ad data, and document any long-term profile responsibilities. A clean closeout protects the artist and the partner. It also makes the next campaign easier because the team knows which accounts are current.
How this access checklist is grounded
Practical notes
- This guide treats access as an operating requirement for release campaigns, label services, and reporting.
- The workflow uses least-privilege permissions because release work often involves outside managers, contractors, labels, video teams, and ad operators.
Source notes
- Spotify for Artists support explains how admins can invite team members and assign access levels: https://support.spotify.com/us/artists/article/adding-team-members/
- Apple Music for Artists support covers managing users and roles for an artist page: https://artists.apple.com/support/1121-manage-access-to-your-artist-page
- YouTube Help explains channel permissions and role-based access in YouTube Studio: https://support.google.com/youtube/answer/9481328
Frequently asked questions
- Should a label-services partner get every artist password?
- No. Give named platform access only for the work in scope, and keep sensitive admin control with the artist-side owner.
- When should platform access be checked?
- Check access before delivery deadlines, pitch windows, video uploads, ad setup, and release-week reporting.
- Who should own two-factor recovery?
- The artist, manager, or long-term admin should own recovery, with a documented backup who is not a temporary contractor.
- Does every campaign need ad-account access?
- No. Only give ad access when paid promotion is included and the campaign owner knows who approves spend.
- What happens after the release report?
- Remove temporary users, archive reports, keep agreed dashboards available, and document what access is needed for the next release.