Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
externalorgmembers [2019_11_22 14:40] jimexternalorgmembers [2022_02_09 12:29] (current) – removed dan
Line 1: Line 1:
-====== External Parties as Org. Members ====== 
-== last updated Nov. 14, 2019 == 
  
-The File Fabric provides many ways to share data with external users, such as Business Group Workspaces: 
- 
-[[businessgroupsharing|https://docs.storagemadeeasy.com/businessgroupsharing 
-]] 
- 
-and Drop Folders: 
- 
-[[https://blog.storagemadeeasy.com/introducing-drop-folder-for-azure-google-nearline-s3-openstack-and-other-cloud-storage-services/ 
-]] 
- 
-but in some situations an organisation may wants to share files with external parties using shared team folders. When this is done the org. admin can make the external parties domain members by adding them as users and restrict their privileges so they can do little except access the files that are being shared with them. Here are some points to consider if you adopt this approach: 
- 
-  * The Member role is assigned automatically to each member that is added to the org.  In most cases this assignment should be removed for the external parties.  That way if a shared folder owner wants to grant access to all internal members of the org., she can grant access to the Members role and exclude the external parties. 
- \\ 
- \\ 
-  * Unless you want to allow the external parties to store files on your storage you should establish the smallest possible storage quota (one MB) for these users. 
- \\ 
- \\ 
-  * You may want to block access to the File Fabric by the external parties through some or all of the supported client program types (devices).  Note that access via at least one device type is needed so the external parties can access the shared folders. 
- \\ 
- \\ 
-The org. admin can control all of settings from the “Organization staff :: Edit User” page.