⭐ User Administration

[Nick_M]

This topic is to collect design material for user administration.

See also the closely related area Member Administration

Purpose

Define a set of services / tools to help Resonate admins to support end users in their journey with the co-op

Scope

User Stories in scope:

Ref	Who	Story
B03	admin	As an administrator I need to own/operate a (semi-) automated member sign-up / greeting process and receive approval / exception alerts.
B07	admin	As an administrator I need access to a log of customer service and security-related events and exception alerts for admin action such as logins, token refresh, password / account recovery
B08	admin	As an administrator I need to execute logged access to a user account recovery or details edit - logged transactions with timestamp and userid in line with data security audit principles
B09	admin	As an administrator, I need to administer role-based access control
B10	admin	As an administrator, I require logging of authentication and access to endpoints for all significant resources / collections.

Mainly focused on services associated with the user object (e.g. password resets) and configuring profiles.

See also:
User Stories full list.

User & Membership Management

Purpose This is a forum post to summarise the user stories related to user and membership management. There’s more detail in the user and membership API specification and deck, but the purpose of this extract and summary is to: explain the context by summarising some overall goals, principles and assumptions; focus more on the user experience in the sign up process (website ‘flows’); think also about the user needs and experience of coop workers who ‘meet and greet’ and administer subscrip…

Joining / Membership Sign Up flows:

Flow Design for Creating Profiles and Joining as a Member

Considerations for ‘Join the Coop’ below the ‘Create your profile’ block: some users will visit this block once and not change their relationship with the Coop thereafter others will return to the page several times as they modify their relationship user and membership information is essentially the same as for listeners, artists and label owners: use a consistent form layout minimise the information to be collected and maintained by the coop do not set up a corresponding stripe user until it …

User API data model:

User API Data model

@merefield Could you give a summary of the current state of the user data model here, and some references to the relevant swagger docs? We need a centralised overview for future building, both on the dev side of things, but also for PMs to understand what they’ve got to work with.

UserAPI end points here: https://github.com/resonatecoop/user-api/blob/master/third_party/OpenAPI/user/user.swagger.json

[richjensen]

@jeremy @piper @brndnkng @replygirl

I believe this is the best documentation for the current USER API. @auggod would know best.

[auggod]

Current User API explorer is here: https://api.resonate.coop/