When creating an App within SplunkWeb, it creates the *nix directory structure with 0700 permissions. Only the owner of the Splunk instance can "access" the directory structure, and no one else (i.e. members of the *nix group cannot view the contents of the directory because the permissions are set to 0700).
I have used setgid on the parent directory, etc/apps, but to no avail.
Is there a proven method to ensure that when an App is created in SplunkWeb that members of the *nix user group will be able to access the App directory structure (i.e. 0740)?