...
- Currently, we don't think that making it anon-public limits editing access; that is, a user can still change the table and save a new version of the Table.
- Currently, opinions are mixed on whether changing the data and/or the schema will trigger a need for reapprovalre-approval, but we should assume that this approval process may be cyclical.
...
All the same things as Use Case #1 but for external groups – deprioritized de-prioritized for now.
Use Case 3: Anonymous Access to Data Deemed "Open Access"
All the same things as Use Case #1 but for more kinds of data – de-prioritized for now.
The broader general case is that Synapse currently does not support any kind of "Open Access" data, despite saying that we do, because we ultimately still have a login requirement to access (download) any data, even data marked for Open Access. This includes Files and Tables, and potentially other kinds of data later on. This limits the kind of content that can be shared in Wikis, which CAN be anonymously viewed, and we've implemented workarounds to this such as allowing anonymous access to files loaded as Wiki Attachments, but not those same files loaded as "Files" in the Files tab. This is incredibly confusing to users and actually introduces more risk than simply allowing (vetted) open access data, because there are no "checks" on data loaded into Wiki Attachments.
...