Labels specific user-features

[LouisLouiseKay]

When a user identifies as a music-label, they should have access to specific features :

• Profile picture displays roster of managed artists
• When a label-user "creates an artist" they should be able to type the name of an artist and request access to this artist account management.
• If an artist has only made "a few releases" under a certain label, the artist should be able to precise during the album creation/editing process that "this album was made with xxxx label".
• When an artist has 3 albums in their account under a label, the label can only see and edit those 3 albums when looking at the artist profile editing page.

To be determined if Labels get full access to artist features, or just to some of them. I'll investigate how bandcamp does it because it's pretty well integrated.

[simonv3]

For the sharing of album management with another (label) account I was thinking of introducing two new fields in the TrackGroup table:

Step 1: changes to current code

• Change the API so that it doesn't reference the user ID of the artist being managed. /user/1/artist/1 becomes /manage/artist/1. This just simplifies some things around logic who can and who can't manage artists. This will require some pretty significant code changes across the app around permission checks. I think most of those already have tests written so that's good.

Step 2: admin can edit artists and trackgroups

• Implement functionality for an admin to edit artists or trackgroups. This should be possible already but is mainly being blocked by logic caused by the complexity of step 1. So once that's implemented we have to test whether this works.

Step 3: transfer artist ownership

• Add a "transferOwnership" endpoint at /manage/artist/:id/transferOwnership that moves an artist to a new userId.
• Add a button on the artist page next to the Delete button that lets an artist do this with a pop up where they enter a userId. The pop up should also explain that this means that the income generated by the artist will go to the new user account.
• Question: do we need the receiving user to confirm the transfer? In which case this is a bit more complicated.

Step 3: Other users can manage artists

• Implement a userCanManageArtist table
• Add logic to the permissions logic for artist editing that checks this table
• Add a differentiator between "owned" artists "managed" artists to a user's profile page. Possible in a new Artists tab?
• Add managed artists to the dropdown menu.
• Figure out any spots in the UI where this might now be broken?

Step 4: Say a different user can receive payouts for an album purchase

• add ownerId to TrackGroup
• When determining where payout store goes, first check trackGroup.ownerId and then trackGroup.artist.userId. Redirect to appropriate Stripe
• On receiving payment confirmation, send email to trackGroup.ownerId before trackGroup.artist.userId

Step 4: Other users can manage trackGroups

managedByUserId	trackGroupId

The first one will be who can "edit" an album.

I have some questions here around who should be allowed to edit an album, and if it could exclude the user who owns the artist account (for ex, a previous label owns the rights of the trackgroup, so the artist shouldn't be able to edit it). That could be TBD for later though

[LouisLouiseKay]

We can absolutely do 3 later. I think ultimately it's not critical wether we go with 1 or 2 because in either cases tensions could arise (because tensions do arise between a label and an artist in real life). We can leave it to "either" for now, see if people complain about that. If the difference in complexity is substantial with just having one manageUser we can even go with (1) but I think (2) is more agnostic and "sort this out yourself".