Notifications Page (Frontend) and Integrate w/ Backend

[ThatMegamind]

Instructions

• Most of the previous tasks have focused on the Catalog and Published Schedule, but one of the other main components of this project is the Notifications Page, which essentially acts as a dashboard for Admin Users
• In this task, you’ll be setting up the main skeleton for this page
• Some of the functionality and design is still TBD (we'll likely move this page to a drawer later), but the main functionality you’ll be implementing today is displaying all “pending users” in a list view
• Pending users are users who have submitted a request to create an account, and need to be approved by an admin

Notes

• Users who are “pending” are those in the Users table whose approved attribute is set to FALSE
• Remember that you’ll need to have the backend running in order for the routes to be used
• To understand the design of this page more, talk with Selina from the design side!

Acceptance Criteria

• The new page can be found at the preexisting /notifications route
• All users whose account requests are pending are displayed in a list view
• User requests can be either approved or rejected with an “Accept” or “Decline” button
• Rejected user requests should result in the user’s row being deleted from the Users table
• Approved user requests should change the user’s approved attribute to TRUE and allow
• All approved users can log into the system
• All rejected and pending users cannot log into the system

Resources

• Chakra List
• User Routes
• Lo-Fi Designs (see “Notifications”)
• DB Model

As always, feel free to message Michael and Michelle if you have any questions!