Sharing a password can feel like the quickest way to let a manager, bandmate or freelancer help with your artist profile. It also makes it harder to control what each person can see and change. Spotify for Artists team access gives each trusted person their own login and a defined access level. That is easier to review, change and remove when a project ends.

This guide explains seven checks to make before you invite anyone. It uses Spotify's current help pages for team roles, invitations, removals and two-step verification. Features and labels can change, so check the live support pages before making an important account decision.

1. List the jobs the person actually needs to do

Start with tasks, not titles. A publicist may need to view audience data. A manager may need to edit the profile and pitch an upcoming release. A bookkeeper may need to manage a payment method. Write down the specific jobs first, then choose the narrowest access level that covers them. This reduces accidental changes and makes future reviews much clearer.

2. Understand Admin, Editor and Reader access

Spotify says Admins, Editors and Readers can all view music and audience statistics, the artist roster and the artist profile. Admins and Editors can edit the profile, pitch upcoming releases, manage campaigns and work with Shopify merch. Only Admin access includes adding or editing payment methods. Reader access is therefore a sensible starting point for someone who only needs reports.

Check Spotify's current access level table

Do not give Admin access just because someone is senior or has worked with you for years. Give it when their tasks genuinely require the extra controls. If you already use Spotify merch, our practical buying-journey checks can help the person responsible understand what needs reviewing.

Read The Hubb's Spotify merch guide

3. Keep Team Admin separate from everyday editing

Spotify describes Team Admin as an additional permission. Team Admins can invite and remove members, change access levels and see team activity. That power is different from editing the artist profile. Keep the number of Team Admins small, but make sure the team is not dependent on one person who may become unavailable. Record who the current Team Admins are in your private working notes.

4. Send an individual invitation

A Team Admin can invite a trusted person on the web through Spotify Manage. Spotify's current steps are to open the team, select Invite, enter the person's details and choose their access level. The person then receives an email with the steps to join. Ask them to use an email account they control and will keep, rather than a shared inbox that several people can open.

Follow Spotify's invitation steps

Before sending the invitation, confirm the spelling of the email address and tell the recipient which team and role to expect. This simple check helps them spot an unexpected or fake message. Never send your own Spotify password or a two-step verification code.

5. Turn on two-step verification

Spotify strongly encourages two-step verification for Spotify for Artists users. It adds a second step after the password. Spotify currently supports an authenticator app, SMS, or both. Each invited person should set it up on their own account and store backup codes somewhere secure. Backup codes should not be shared, and each code can only be used once.

Set up Spotify for Artists two-step verification

6. Test the role with a real task

After the invitation is accepted, test one harmless task together. A Reader might confirm that they can open the audience statistics they need. An Editor might check that the profile tools are visible without changing anything. If a person cannot do an agreed task, change the role deliberately instead of handing over a password as a shortcut.

Use the same careful approach for public profile work. Check the artist name, image, links and release details before anyone saves a change. The Hubb's profile protection checklist explains how to review releases and report music on the wrong profile.

Review The Hubb's Spotify artist profile protection guide

7. Review and remove access when work ends

Put a regular team review in your release routine. Check the list after a tour, campaign, management change or freelance job. Spotify says Team Admins can remove a member through Spotify Manage on the web, or through Your teams in the Spotify for Artists app. Removing old access is part of closing the job, not a judgement on the person.

See Spotify's current removal steps

A simple Spotify for Artists team access checklist

  • Write down the exact tasks the person needs to complete.
  • Choose Reader, Editor or Admin using Spotify's current table.
  • Limit Team Admin permission to people who manage membership.
  • Invite the person's own email address instead of sharing a password.
  • Ask every member to enable two-step verification and protect backup codes.
  • Test one real task after access is accepted.
  • Review the team after each project and remove access that is no longer needed.

Make access part of release planning

Good access control should support the music, not slow it down. Decide who owns each task before a release gets busy, give them only the tools they need, and set a date to review the team. You will have a clearer handover, fewer shared secrets and a much easier way to close access when the work is finished.

Use The Hubb's four-week music release timeline

Match the role to a real task

  • Someone reviewing audience data may only need Reader access.
  • Someone updating the artist profile or pitching releases may need Editor access.
  • Someone managing payment methods may need Admin access.
  • Someone inviting or removing members needs the separate Team Admin permission.

These are task examples. Check Spotify's live permissions table before sending an invitation. A job title does not automatically justify the broadest role.

A project access record

Person and confirmed email: [details]
Artist team: [correct team]
Tasks: [specific jobs]
App role: [Reader, Editor or Admin]
Team Admin needed: [yes or no, with reason]
Project end or review date: [date]
Removed or adjusted on: [date]

Keep this private. Check access again when a freelance job or management arrangement ends. Do not share the owner password or recovery codes. The same principle applies to YouTube channel permissions.