Configuration Precedence
Connect Server gives precedence to settings as follows, where user settings have the highest priority and default settings have the lowest.
- User
- Group (if a user belongs to more than one group, a precedence can be set for each group.)
- Global
- Default
The table below shows the setting values that are applied to user aspera_user_1 in bold when that user is also a member of several groups and global settings are configured. In this example, aspera_user_1 is a member of both the admin and xfer groups. The admin group's precedence setting is 0, which supersedes the xfer group's setting of 1:
| Options | User aspera_user_1's Settings | Group admin's Settings | Group xfer's Settings | Global Settings | Default Settings |
|---|---|---|---|---|---|
| Target rate | 5M | 10M | 15M | 40M | 45M |
| Min rate | n/a | 2M | 8M | 3M | 0 |
| Policy | n/a | n/a | Low | Fair | Fair |
| Docroot | n/a | n/a | n/a | /pod/$(name) | n/a |
| Encryption | n/a | n/a | n/a | n/a | any |
Configuring Precedence of Groups
You can configure a group's precedence from the GUI or by editing aspera.conf.
GUI:
To configure it from the GUI, launch the application and click Configuration.
In the Server Configuration dialog, select the Groups tab, choose a group, and select the Precedence tab. (The Precedence tab does not appear if there are no groups.) Select the Override checkbox and enter a precedence number for the group.
