Currently, there is no singular internal ID that represents a logged-in user. This is a problem because we need to log down user-related activities and configure user-related settings.
User-related activities:
A user’s actions must be recorded for auditing, debugging, and GDPR purposes—There are many situations where a user’s steps need to be retraced to find out where a mistake was made, when exactly it was made, and whether it had an impact on a task or a customer’s private information.
User data and preferences:
First / last name
Email address
Users need to be able to manage their notification settings. Notifications can be sent, for example, whenever a new task is created, when a task is assigned to a specific user, when a message arrives from a customer, etc.
MVP
The User Profile should, at a minimum:
Be created automatically behind the scenes the first time they log in.
It should generate an internal, nondescript id for the user.
Logged-in users should be able to edit their profile (first/last name, email address)
Logged-in users should be able to change their notification settings.
Currently, there is no singular internal ID that represents a logged-in user. This is a problem because we need to log down user-related activities and configure user-related settings.
User-related activities:
A user’s actions must be recorded for auditing, debugging, and GDPR purposes—There are many situations where a user’s steps need to be retraced to find out where a mistake was made, when exactly it was made, and whether it had an impact on a task or a customer’s private information.
User data and preferences:
MVP
The User Profile should, at a minimum: