Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Starting September 10, 2024, all (new and existing) Engine users will be required to provide an attestation to the EverBright Code of Conduct before accessing Engine. This will be done through an acknowledgement screen that appears on login (first login for new users) where a user must read and agree to the Code of Conduct. Currently all Engine users will be required to complete the EverBright Code of Conduct annually and it requires a review of the EverBright training portal.

image-20240807-233531.png

 

FAQ's

 

Question: Can a user bypass the Code of Conduct, access Engine and complete the attestation later?

Answer: A user cannot access Engine unless he/she has completed the Code of Conduct.

 

Question: Can a user complete part of the Code of Conduct and then return to complete the remaining sections in a different session?

Answer: Users must complete the entire Code of Conduct in one session as the state of partial completion is not saved.

 

Question: Can an installer log in as (impersonate) a user that has not completed the Code of Conduct?

Answer: Users that have not completed the Code of Conduct and do not have a special role associated to the account cannot be logged in as until the CoC is completed.

 

Question: Will an account that has been transferred by switching email ID's be required to redo the Code of Conduct?

Answer: Any account that has a change in email ID associated with it will be required to redo the Code of Conduct on first login post change.

 

Question: How often will a user be required to complete the Code of Conduct?

Answer: As of today, users will be prompted to complete the Code of Conduct one year after they last signed it but the frequency of the same may change in the future.

Example: Tom signed the CoC on 4th October, 2024. He will be prompted to resign the Code of Conduct a year later before being granted access to the platform.

  • No labels