It may be beneficial in the environment to configure an inbox for delivery of content for admin review, without sharing that content with all other users that have access to a share.
The following write-only drop-box configuration demonstrates an example classroom configuration, where students may submit content for instructor retrieval.
Create a share if needed
Assign permissions when prompted
This EVO sees Active Directory users and groups from both a parent and child domain, and will be configured for "teachers" and "students" groups.
Assign the permissions that are generally best for default use
If EDIT ACL is clicked again, the standard permissions for the share level are shown
In this example, a member of the teachers group (teacher1) mounts the volume and creates one directory for student reference, and another one for assignments
To adjust permissions for directories on EVO, navigate to System > File Navigator and choose the intended share from the drop-down menu on the left -- in this example, the share name is "inbox"
Select the intended directory and then EDIT ACL
Since the default permissions are inherited, they're view-only. Choose DISABLE INHERITANCE to modify them.
There's no need to remove all existing permissions in this case, so click CONVERT INHERITED PERMISSIONS INTO EXPLICIT to allow editing
Click the three dots next to the user/group you'd like to restrict and choose "Edit"
Choose "Allow" for the type, and apply to "This folder and subfolders"
Click the down arrow next to Read, and allow all except for "Traverse folder/Execute file"
Grant write access, and disallow the Delete options
Now that directories are available for writing, click the plus symbol to add a new permission for files
Select the user/group, use Type "Allow", apply to "Files only", and check Write.
There will now be two custom permissions listed
When a member of the "students" group mounts the share, they're able to add to the write-only directory without view of files within
When a member of the "teachers" group mounts the share, they're able to see all content in the directory
Note: ShareBrowser 6.1.5 is not compatible with this type of custom permissions configuration and should not be used to submit content to a write-only location.