For complex Synapse projects, administrators manage many folders with different sharing settings a wide variety of data that requires different permissions for different user groups. In this scenario, creating a permission model for the project system for managing data access with Synapse teams is recommended. A permission model helps you This method allows you to group users together according to the level of access they require . These groups can then be managed as a whole, rather than as individual usersand then assign permissions to the entire team rather than to many individuals.
When creating a permissions model for your projectteams to manage data access, consider the following questions:
...
Recommended Team Types
For many collaborations, there is a small group of users administers the project, a larger group who contributes data, and an even larger group who downloads the project contentsdownloads that data for their independent research. In these cases, we recommend creating groups for each of these permission types: an administrative team with “administer” permissions, a data curation or content creation team with “can edit” permissions, and a downloading team with “can view/download” permissions. If you intend to make your content publicly viewable, this third team is not necessary; you can click on Make Public to share your project more broadly.
Because permissions are additive, a user who is in all three teams has the permissions of the highest level granted. In other words, if you add a single user to three different teams, “administer”, “can edit”, and “download”, the user will have “administer” permissions. If you remove that user from the “administer” team, they will have “can edit” permissions.
Local Sharing Settings
...