You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 27, 2023. It is now read-only.
It might be necessary to show most personal details of one participant to another, but it should be enforced that if a validation strategy exists in that instance, then only approved users can see personal details of other users.
For example, in m4h, hospitals have to be approved, therefore they should only be able to see personal details once they are an approved hospital with a validated email.
In a system where approvals are not used, it should be configurable and clearly documented, which fields are visible for other participants of both types.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It might be necessary to show most personal details of one participant to another, but it should be enforced that if a validation strategy exists in that instance, then only approved users can see personal details of other users.
For example, in m4h, hospitals have to be approved, therefore they should only be able to see personal details once they are an approved hospital with a validated email.
In a system where approvals are not used, it should be configurable and clearly documented, which fields are visible for other participants of both types.
The text was updated successfully, but these errors were encountered: