Sprint # 5 Considerations:

[tien-han]

Sprint # 5 Considerations:

Note: We don't have to let an admin edit a user's application

1. Login that stores user password not in plain text (hash and salt passwords)
2. Might be good to let admin see the user side (in case the admin needs to troubleshoot what happens with a user)
3. Check what the website looks like on mobile
4. Make sure that user A can only see and work on user A applications
   1. $_SESSION['UID']
5. Admin should see everything (all applications) and be able to edit the same application (the application that a user has added in)
6. Should a user be able to delete themselves?
7. Should an admin be able to remove themselves as an admin?
   1. Maybe they shouldn't? So you need an admin to remove you? That way, there always has to be at least one admin.
8. User should be able to change their own password
9. Optional: A user should be able to see if an admin has made a change
10. Make sure a user can't access another user's applications/data
11. Optional: Password recovery?