Define repository access rules

You can configure Subversion's native authorization rules to give users access to a whole repository, or to a specific path within a repository.

To edit repository access rules, you need the ROLE_ADMIN or ROLE_ADMIN_REPO role.

Note: Subversion 1.8 checks access rules before showing a list of repositories. If you do not have read access to a repository, you will no longer see it in the list. With Subversion Edge 4.0.0 and later, the list of repositories displayed respects these rules as well.

Select Repositories in the main navigation bar.
Click Access Rules.
Click Edit and make your changes.
Note: The file is locked to other users until you click Save or Cancel.
- The format for an entry is [repositoryname:/path/within/repos].
  Example 1:
```
[dev:/branches/components/xxx]
user1 = rw                                 
user2 = r 
user3 =                           
```
  This gives "user1" read and write access to the "/branches/components/xxx" directory in the "dev" repository and read-only access to "user2". User "user3" is denied access to this directory, since the username has neither "r" nor "w" assigned.
  Example 2:
```
[/]
* = rw
```
  This gives all users read and write access to all repositories.
- You can define groups in a section named [groups] and refer to groups within rules using @groupname.
  Example:
```
[groups]                                    
mgrs = user1, user2
                               
[dev:/tags]
* = r
@mgrs = rw
```
  This gives the users in the group "mgrs" read as well as write access to the "tags" directory in the "dev" repository. All other users have read access to this directory.
- Groups can contain other groups.
  Example:
```
[groups]
mgrs = user1, user2 
engrs = engr1, engr2 
allgroups = @mgrs, @engrs
```
Click Save.