Terminology
| Term | What it means |
|---|---|
| sharer | The user that shares content |
| sharee | The user whose content is shared with |
| assign permissions | same as "share content" |
| disinheritance | to override the parent folder's permissions |
| explicit sharing | to add permissions using the sharee's account directly |
| implicit sharing | to share folder to the enterprise using a link or create content within a shared folder |
On Sharing
SkySync transfers content and migrates permissions in that sequence. This is mainly because platforms expose shared content differently. In other words, we transfer content first, then apply permissions after the content is transferred. Applying permissions can have unintended consequences at the destination depending on how the destination exposes shared content after the destinations are applied. This is why we have the ability to exclude shared content from the source so that content is not duplicated on the destination after permissions are applied.
...
In SkySync, using Lynn's account and regardless of
- When GoogleDrive.
...
- AllowSharedWithMe is false, JuanFolder1, JuanFolder1/SubfolderByLynn and JuanFolder1/JuanFolder2 are considered shared. JuanFolder1/LynnFolder1 is not considered shared.
- When GoogleDrive.AllowSharedWithMe is true, JuanFolder1, JuanFolder1/JuanFolder2, JuanFolder1/SubfolderByLynn and JuanFolder1/SubfolderByLynn LynnFolder1 are all considered shared. This keeps consistency with Box's behavior.
In SkySync, using Juan's account:
...