Project-level Users #47
Description
There is a need to allow mother tongue translators (MTT) that do not make large use of technology to work on translations. The system should allow for MTTs to access work assigned to them without requiring an email and traditional authentication.
This can be solved using a tokenized link that can be shared with them that allows access to the resources assigned to that translator.
Project Users would be created only in the Application DB, not in Auth0.
Project Manager should be responsible for creating the project-level users and sharing the link(s).
Upon user creation, we generate an access token that should be passed with API requests.
There should be a text field that acts as a user display name so that PMs can differentiate between the translators and make assignments easily.
CW: I think there may be a need for two levels of project-level users. The second level will be a user that can edit anything in the project. This is to facilitate the checking phases and the lock/unlock system. Or maybe we just go with this second level??
- this could possibly be a role for the user as well. This way all users have almost 100% same functionality and we are not trying to implement dual logic for basically the same concept.
For acceptance of terms and and privacy policy - splash page upon first visit:
- Displays message about Fluent and what it is with a link to terms and privacy
- Click 'continue' or close the tab