Frequently asked questions for collaborators and teams #

If you have any questions or need any information, please send a request to support@revas.app.

Contributor fails to log in with Gmail email (@gmail.com) #

Google emails make no distinction in the presence of dots within the email. For Google mario.rossi@gmail.com, mariorossi@gmail.com and marioro.ssi@gmail.com are all identical. RevasOS for security reasons saves the user with the exact email entered at signup, so for RevasOS mario.rossi@gmail.com, mariorossi@gmail.com and marioro.ssi@gmail.com are all different emails. This behavior is specific only to Google so to cover the other providers as well the precise enrollment email is required to access RevasOS.

So if the user signed up with mario.rossi@gmail.com but logs in with mariorossi@gmail.com, on Google the login works but on RevasOS it does not.

In this case, ask what email he or she is logging in with: the two emails must be identical. If, on the other hand, the contributor does "Sign in with Google," ask to check the email address selected for sign-in.

The invitation email does not reach the contributor #

If you added a contributor with an email address and the email isn't delievered:

1. Controlla che l'email inserita sia scritta corretta e non ci siano errori di battitura o caratteri incorretti. Chiedi eventualmente conferma al collaboratore;
2. If the email is correct, try asking the contributor if the email he gave you is the email he actually logged into RevasOS with.
   • You can ask what is the email to which the access codes came if he logged in with the code. You can possibly ask to logout and log in again,
   • If no codes arrived because he did "Sign in with Google," ask him to logout and log in again. If by logging in the employee does not see the user creation screen, it means that that email is the one he or she logged in with Google
3. Sand the email is correct, ask to check the spam folder, archive, or trash. It could be that counter or archiving systems or oversights have inadvertently hidden the email
4. If the email was not archived, deleted, or placed in spam, try removing the contributor and inviting him or her again by email,
5. If the email does not arrive in this one either, contact us at support@revas.app.

The contributor is unable to access the organization. #

If the contributor cannot access:

1. Ask if they can login with code or login with Google on the authentication screen. If they cannot login,
   • ask if they entered the last code they received and if they did not enter it after three minutes since codes expire in that time frame. In that case, ask them to send a new code and log in again. If they continue to see the error, , contact us at support@revas.app
   • ask if they are properly receiving the emails with the login codes, ask them to check their spam, archive and/or trash folders,
2. If they receive emails correctly and are able to access the system, but are not in the correct organization or see an organization creation shcerm, ask them to check the email for typos,
3. If the email is written correctly, check that the email he is logging in with is the email you used to add him to the organization's contributors. Try sending it to him and asking for confirmation,
4. If the emails match and the contributor still can't get access, contact us at support@revas.app