I have a question regarding best practice for setting up our folder structure/ hierarchy...
In this organisation we have (currently) two very separate use cases for the use of ShareFile:
- UC1: the "BCP" use case: as a cloud-based repository of documents to be accessed in the event of an 'emergency' (non-availability of the source system, natural disaster, etc.). There are approx. 25 folders each with one report that is refreshed periodically. Access to each folder is limited to specific groups of users. Permissions for most users are as limited as we have been able to make them: read and download only;
- UC2: the "classic file sharing" use case: we need to exchange files with various external organisations. A completely different set of users will use much of ShareFile's functionality to upload files, notification emails sent, files downloaded, links expire after n weeks, etc. etc.
Based partly on our reading of advice in the ShareFile Best Practice document (via link here: https://support.citrix.com/article/CTX227202 ) to keep the structure as flat as possible we have set up the folder structure as follows:
Root > BCP Folder 1
BCP Folder 2
BCP Folder 3
BCP Folder n
External Client A
External Client B
i.e. all folders are sub-folders directly off root.
However looking more closely at the way permissions are inherited/ cascaded down to sub-folders would we be better to set up our hierarchy as:
Root > BCP > Folder 1
External > Client A
i.e. introduce a "use case" sub-folder under root, then have the sub-folders under those.
What would Citrix recommend as a preferred folder structure in our circumstance? We still have some time before full production go-live so do have a window to change our set-up.
Be the first to post a reply!