Synapse has two ways to control who can access your content. Sharing Settings determine who can access content, and is akin to individual or group (team) permissions. Conditions for Use determine how data can be used by those users who have been granted access. All content in Synapse has Sharing Settings but not all content has Conditions for Use. See the Sharing Settings article for information about those settings - this article covers conditions for use only.
Some data requires data governance to appropriately manage its use. In Synapse this data is called Controlled Data and it is protected by Conditions for Use, typically applied in order to comply with the terms under which the data were collected or with other human subjects regulations. For example, human ‘omic’ data may have Conditions for Use imposed by informed consent requirements, legal contracts, or other privacy requirements. It is also appropriate to add Condition for Use to data collected from “vulnerable” populations and to content that could potentially harm individuals or groups if misused. If you have any questions about whether conditions for use should be applied to your data, please contact our Access and Compliance Team (ACT).
Conditions for Use vary broadly. Some examples include:
Additionally, use of certain data may require independent review and monitoring of research by an ethics committee (for example, an IRB). This ensures that use of the data meets all applicable human subjects research regulations.
Controlled Data requires appropriate Conditions for Use, can only be downloaded and used by authorized Synapse users, and is not transferable unless explicitly specified otherwise. In other words, you cannot share Controlled Data with collaborators; aach Synapse user wishing to access controlled data must individually agree to the conditions for use to access that data.
It is important to note that Conditions for Use cannot be set for Synapse Wikis
or Discussion Forums
: they are not designed to house data and therefore do not have conditions for use as a feature.
Examples of Controlled Data include:
Synapse Open Data is data that does not require Conditions for Use. Typically, open data is:
If you would like to set Conditions for Use for an entire Project
, please contact the Synapse Access and Compliance Team (ACT) directly for assistance.
By default, content within a Folder
or Project inherit the Conditions for Use of the parent Folder or Project. As with sharing settings, you can set local conditions for use for individual Folders, Files
and Tables
but only in addition to the existing parent Project/Folder’s conditions for use. In other words, all content within a Folder or Project has, at a minimum, the Conditions for Use of its parent Folder or Project, and may have additional local conditions for use as needed. You cannot create a Folder, File, or Table that has fewer conditions for use than its parent or that has conditions for use that conflict with the conditions for use of the parent.
To set Conditions for Use for Folders, Files, and Tables in Synapse, nagivate to the content in question and use the popup Conditions for Use dialogue box. If you select that you would like to set conditions for use for your content, you are asked if the Folder, File or Table contains, “sensitive human data that must be protected.” If you answer “yes,” the ACT will reach out to you to assist in setting the appropriate Conditions for Use. If you answer “no,” but still feel that your Folder, File or Table requires Conditions for Use, contact the ACT for further discussion (act@synapse.org).
Try posting a question to our Forum.
Let us know what was unclear or what has not been covered. Reader feedback is key to making the documentation better, so please let us know or open an issue in our Github repository (Sage-Bionetworks/synapseDocs).