Can I create a Release from Different Accounts?

The same account (email) must be used to create all the parts involved in a release. Creating the release with one End User account and adding the tracks with another one (or vice versa) is not the correct way to use the platform. It can cause problems when it comes to saving data and distributing the content.

This is why all metadata of the same release should be created from the same End User's account (not the Admin account).

What if I (Admin) have to create new tracks for the End User?

I (Admin) have already created the tracks. Can I move them to the user's account?

What if I (Admin) have to create new tracks for the End User?

If the Admin wants to create a new release for an End User, add new tracks, or do any modification to a release, it is necessary to swap accounts and, for example, create new tracks, from the End User's account.

To do so, the Admin should click on the arrow next to his/her name and select the option "Change user":

Introduce the email associated with the End User account and click on "Ok":

The log-in might take some time to manage the related permissions to switch accounts, please wait for some seconds until the log-in is completed. When you see that the login is completed, proceed with the modifications required.

I (Admin) have already created the tracks. Can I move them to the user's account?

No, the Admin can't move tracks from one account to another. Tracks must be created again from the End User's account, otherwise, even though moved into the right account, the End User will not have access to the tracks' information (meaning the End User will not be able to enter any of these tracks, as well as control the royalties that will be generated from these tracks).

The Admin must delete the tracks created from its account, swap accounts, and create them again from the End User's account.

Please note that moving tracks from one account to another is considered a bad practice which can cause issues to the content during the distribution and later (ie. losing royalties data). In case the Admin decides to move a track this way, SonoSuite is not responsible for any possible failures that may occur or to fix the matter.