Setting up file system access permissions

This section explains the file system permissions required for administrators, build engineers, and other users to properly set up, manage, and operate projects.

On Linux, the IT team and system administrator set permissions for users who share administration privileges for the same projects_root. Such users should be members of the same user group, with UMASK set to allow all group members to have read/write permissions.

Permissions for administrators and build engineers

To perform certain tasks, ensure that your administrators and build engineers (and depending on your organization, other required users or groups) have the following access permissions for directories and files.

Permissions may need to be granted for each new project.
Task Required access permissions for directories and files
  Projects_root directory Installation directory Source code that will be used for projects
Start and stop the Validate servers read/write read read
Create and manage projects read/write read read
Analyze projects read/write read read

Permissions for projects built from tables

Build data is created using the user ID of the user who starts the build. If the build runs on one machine and the projects_root exists on another machine, the tables are copied from the build to the projects_root.

The user who loads the tables into the database with validate admin load must have read/write access to the tables directory and subcontents. To allow such access, you may need to change the permissions on the build machine's tables directory and subcontents.

Permissions for other users

All users who will work within a projects_root directory require access to it. If you create a new projects_root using validate service setup, give read/write access to all users who will work within the projects_root directory.