With the help of the given information, create a Class Diagram representing the model for user authentication and management.

Code&Code is a small company dedicated to Software Development. Their engineering team, to which you belong, is working on writing a Web Application as an MVP for a new customer.

The code name for this App is "Loggy", which is meant to offer functionality for a personal journal where users can log their daily activities through text, image, voice, and video.

The main functionality for logging activities and annotating those logs with text, image, voice, or video was completed as part of the first iteration. But all this functionality works for a single user only. They still must work on some other functionality as grouping logs in the project and server transcoding. Still, before moving forward, they have decided to complete the current version with support for multiple users, for which they are considering doing a full-scale module for user authentication.

As for any other system that supports multiple users, the user authentication module must include:

Sign-up.

A self-service registration module where users can sign up themselves. The minimal information to register is email and username, full name, and password, but users can also add some extra information such as the avatar/photo, and first and last name.

Email verification.

An email is sent after the registration, so the account creation is pending. The email includes a unique link used for activating the account and can be used only once.

Resend email for verification. Users who have already signed up but have not verified their account can request the email for verification to be sent again.

Password recovery.

Users can recover their password by requesting an email to do so. The email includes a unique link to be used only once, that directs the user to a page for setting up a new password.

Password changed. Users can change their current password if they have signed in.

Profile change. Users can change their display name if they have signed in.

Additionally, the developers want to offer the option for enabling and disabling features and allowing access to the posts per role, so they want to consider including support for multiple roles per user. The initial roles would be Admin, Author (authenticated users who have full capabilities for publishing), Subscriber (authenticated users with limited capabilities, can only access publications), and Guest (non-authenticated users who may have access to posts depending on the permissions granted).