-
-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix project bug that prevents project members from confirming matches on project encounters #957
Comments
Adding question tag so the details of the scope can be worked out. |
this can be done through projects. create a project and add the user to it |
But the user can't confirm matches on the encounters in that project unless a collaboration exists between them |
haaa that might be a bug 😆 This is the weirdness between read, match, and edit that isn't always handled consistently. The intention of projects was to grant read-and-match access to a subset of data that all users in the project can add to and manage |
Oh, that's a relief then. If only because users find it annoying that they have to take this extra step to make their project management functional. I'll write a separate ticket for it later today unless you beat me to it. |
have at it :D Just rework this one? |
Ok, the ticket's been rewritten and and tagged as a bug |
Expected behavior
Adding users to a project gives them access to those project encounters and the ability to confirm matches on them
Current behavior
Users in a project can view the encounters in that project but are unable to confirm matches for those encounters without a collaboration in place from the encounter owner. Because collaborations allow view or edit access to all of a user's encounter data, this workaround isn't ideal for users who are working with sensitive data.
Community link
https://community.wildme.org/t/collaborations-on-specific-project-sites-only/4521
The text was updated successfully, but these errors were encountered: