Comment on page
🔒 Configure metadata access and privacy by Project
Projects now have an icon
:share:next to their title, that will show if a project is
showing the project is Private.
And this will be blue and active if the current user can modify its sharing permissions. When clicking the icon a modal to modify sharing settings will open:
Project Sharing Settings Modal, when clicking the
This will allow to configure which users can view and who can share permissions:
- By default: every superuser and the project owner can always view and share. And change the project visibility (Public/Private).
- The ones that can view can see all project metadata, experiments, analyses, submissions, etc.
- The ones that can share can modify the project settings, by adding new users to view and/or share.
Similarly, a Project's Sharing Settings can be optionally defined when creating a new project. It will be
publicalways by default (In the screenshot shows
privateto show the available options in the form when private is selected).
What metadata can be private?
In practical terms, the metadata of any model (
Submission, Analysis)linked to an
Experimentthat belongs exclusively to private
Projects, it will look like if it doesn't exist in the database for a user that doesn't have access to any of those private projects.
There are 5 samples, where some belong to
Project 1(🔒Private) and
Project 2(📖 Public)
- An user with access to the private
Project 1will see all the
Experimentswith the following Individual Tree:
- An user without access to the private
Project 1will see only see the
Experimentsthat belong to the public
Project 2, with the following Individual Tree: