List view
- No due date•2/5 issues closed
- No due date•0/1 issues closed
- No due date
- No due date
- No due date•1/3 issues closed
- No due date•1/2 issues closed
- No due date
- No due date•0/1 issues closed
- No due date
- No due date
The screen should show a list of all approved users of the application. A user record should include: * User display name (User First name, User Last Name) * Email Address - Should be clickable and open a new email draft * Phone number - Should be clickable and open a new phone call * User role There should be actions associated with each user: * Modify - Once clicked, the admin user will be prompted via a popup to edit information for the user. The information shown to the user should be: | Field | Notes | Editable | | --- | --- | --- | | User First Name | | Y | | User Last Name | | Y | | User Email | Should be clickable and open a new email draft | N | | User Phone Number | Should be clickable and open a new phone call | Y | | User Pronouns | | Y | | User Role | | Y | * **Save:** Updates the requested information for the user. * **Cancel** Closes the modal window, giving the admin an out. All text on the site should be set up as stubs and allow for multi-lingual support.
No due date•1/1 issues closedUsers that have requested access to the application but have yet to be approved by an admin user will be referred to as pending new users. Screen should show a list of pending new users that have requested access to the application. A user record should include: - User display name (User First name, User Last Name) - Email Address - Should be clickable and open a new email draft - Phone number - Should be clickable and open a new phone call There should be actions associated with each pending new user: - Review - Once clicked the admin user will be prompted via a popup to confirm the requested information for the user. The information shown to the user should be: - User display name (User First name, User Last Name) - User email - Should be clickable and open a new email draft - User Phone number - Should be clickable and open a new phone call At this point the admin user will have the opportunity to update the requested role for the user. **Actions at bottom of popup:** - **Approve:** User would be marked as approved in the system. A system generated email would be sent to the user alerting them to the approval of their request and ability to use the application. - **Deny:** User record would be removed from the system. A system generated email would be sent to the user alerting them to the denial of their request. - **Cancel** Closes the modal window giving the admin an out. All text on the site should be set up as stubs and allow for multi lingual support.
No due date•1/1 issues closedRegister screen should be presented to the user when the user is choosing to create an account. This screen should pull information from the appropriate OAUTH provider if possible. The screen should prompt for: | Field | Data Type | Required | | ------ | ----- | ------ | | First Name | Text Field | Y | | Last Name | Text Field | Y | | Email | Text Field - Validate Valid Email | Y | | Phone Number | Text Field - Validate Valid Phone | Y | | Role | Drop Down with Values for Mentor / Parent | Y | | Pronoun | Text Field | N | Check box at the end of the sign up form should be included with some text to be approved by business around agreeing to apps terms and conditions. Creating an account should inform the user that the created account will require approval and will take some time. All text on the site should be set up as stubs and allow for multi lingual support.
No due dateLogin screen should allow any user(Mentor, Parent, and or Admin) to log into the application. The user will be able so sign in via Google, Facebook and at a later time via normal email. The page should have project friendship logo on the page. New users should be able to register for the application via any ( Google, Facebook and at a later time via normal email) of the authentication methods. A newly registered user would be logged into the system and await approval from an Admin users, at which time they would be granted full access to the system. All text on the site should be set up as stubs and allow for multi lingual support.
No due date