Seem like very generic and broad user story that needs to be broken down into specifics… Eg.
As a user group owner, I need to edit the name, description and other public information so that I can display a consistent profile for the ‘persona’ that this usergroup represents
As a user group owner I need to manage the public sharing of my profile so that I can manage my privacy.
We should avoid that and perhaps refer the player use cases to do with user personas / profiles (user groups), to the corresponding detail in the back end user and membership API…
The player user story could then focus on the navigation, ‘flow’ and presentation of the user and membership API features / stories.
There are obv. a lot more user stories around tracks and releases which also need to be written up nicely.