Controlling access with security groups

The Security Groups window is used to manage security groups and settings. Many users will not have access to this view. This view includes group name, description, and security permissions information.

Server security is set in security groups. The commands you enable or disable in a security group apply to all repositories and branches in the mainline branch. See Adding security groups.

Server security commands are grouped in the following categories:

  • General—Common Surround SCM actions (e.g., Generate Reports, Edit Own Email Notifications)
  • Admin—Administrative commands (e.g., Edit Server Options, Void Check Out)
  • Users—User account management commands (e.g., Retrieve User, Delete User)
  • Groups—Security group management commands (e.g., Add Security Group)
  • Files—File management commands (e.g., Add File, Change File Type)
  • Branch—Branch management commands (e.g., Create Baseline Branch, Promote Branch)

See Security commands for information about the commands in each category and what they provide access to.

Users do not need read/write access to the database directory on the Surround SCM Server. Only the server requires read/write access to this directory. All access permissions are controlled using Surround SCM and the changes are made by the server in the database. This adds an additional level of security and prevents users from making changes directly to the files using a third-party editor and bypassing version control.