Technical notes about permissions and security
All data stored in CLC Server file system locations are owned by the user that runs the CLC Server process. Changing the ownership of the files using standard system tools is not recommended and will usually lead to serious problems with data indexing and hamper your work on the CLC Server.
One implication of the above ownership setup is that without permissions enabled on a file system location, all users logging into the CLC Server are able to access all data within that file system location, and write data to that file system locations. All files created within such a file system location are then also accessible to all users of the CLC Server.
Group-based and "user homes" permissions on file system locations are additional layers within the CLC Server, and are not part of your operating system's permission system. This means that enabling and configuring permissions on server locations only affects users accessing data through CLC tools (e.g. using a CLC Workbench, the CLC Server Command Line Tools, the CLC Server web interface or the Server API). If users have direct access to the data, using for example general system tools, permissions set on the data via the CLC Server has no effect.
In addition, when the "User homes" option is selected for a file system location, any existing group permissions are not applied and data placed directly within the top level folder of that file system location will readable by any user.