One of the first things to do, before you start adding security groups, is to group users together based on function. It may be helpful to create a list of the types of users who will be accessing Surround SCM and what their needs are. You should also consider your company’s process and define roles and permissions accordingly. A strong security model allows you to be flexible in assigning access without risking data integrity. The following questions can help you get started:
Did you know? |
For example, a project team might includes one or more of the following: An administrator who has access to all commands. A project lead who has access to most commands but is restricted from such things as creating mainline branches, adding users, or editing server options. One or more developers who have access to most file and branch commands but are restricted from most admin, user, and group commands. One or more testers who only have access to basic commands such as getting and viewing files. A customer who is restricted to viewing one repository. |