Skip to content
Snippets Groups Projects
Commit a15c82f2 authored by elisabet hein's avatar elisabet hein
Browse files

Update README.md

parent 3a0a1d1b
No related branches found
No related tags found
No related merge requests found
......@@ -74,25 +74,26 @@ This project is owned by the Estonian Wildlife Center and is not open source.
### Documentation
#### Description of the general workflow:
1. The user opens the application and is on a welcome page that describes the organization.
- The user opens the application and is on a welcome page that describes the organization.
What the user can do without logging in:
2. The user can navigate to the alert page to report an injured animal.
3. The user can navigate to the registration page to create an application to become a volunteer.
4. The user can navigate to the login page and insert their email and password to log in.
- The user can navigate to the alert page to report an injured animal.
- The user can navigate to the registration page to create an application to become a volunteer.
- The user can navigate to the login page and insert their email and password to log in.
What happens when user logs in:
5. The server create a token for them, which they can use to access the main application and its features.
6. The token will expire after 1 hour.
7. If the token is expired the frontend should redirect the user to the login page. This can be done by checking the backend's response and handling un-authorization with logging out.
8. If the un-authorization is not handled, the user will be stuck in the application without the ability to access any features and probably error messages.
9. If the token is not expired the user should be logged in after refreshing the page and even when closing the application and reopening within an hour.
- The server create a token for them, which they can use to access the main application and its features.
- The token will expire after 1 hour.
- If the token is expired the frontend should redirect the user to the login page. This can be done by checking the backend's response and handling un-authorization with logging out.
- If the un-authorization is not handled, the user will be stuck in the application without the ability to access any features and probably error messages.
- If the token is not expired the user should be logged in after refreshing the page and even when closing the application and reopening within an hour.
What the user can do after logging in:
10. The user can navigate between the different pages of the application defined in the navigation bar.
11. The user can go to their own profile.
12. The user can log out.
- The user can navigate between the different pages of the application defined in the navigation bar.
- The user can go to their own profile.
- The user can log out.
#### Backend
##### Entities
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment