Configure computers with Connect Configurations#
A Connect Configuration is a named set of Connect settings enforced on computers or Access Groups. Use Connect Configurations to apply the same settings to many computers from the Teams dashboard and to prevent local users from changing them. For example, enable a watermark for every computer in an Access Group, or route a site's connections through your own relay servers.
Applies to#
- Jump Desktop for Teams Enterprise plan.
- Team administrators.
- Hosts running Jump Desktop Connect on Windows, macOS, or Linux Alpha.
Create a configuration#
- In the Teams dashboard, open your team. Under Tasks, click Connect Settings.
- Click New Configuration.
-
Enter a Configuration Name and set the required values. To view a setting's description, hover over its name.

-
Click Save. The assign dialog opens.
Settings are grouped by category:
| Category | Examples |
|---|---|
| Updates | Update Channel, Automatic Updates |
| Remote access settings | Screen Sharing, Add Remote Access Users, Allow Cloud Connections, Sleep Override |
| Fluid Connections | Fluid Enabled, Manual Fluid Connections, Maximum Concurrent Connections |
| Fluid Settings | Clipboard Sharing, Local Authentication Restrictions, Watermark, Idle Timeout, Max Session Duration, codec and color settings (see Codecs and hardware encoding), and bandwidth limits (see Get the best performance) |
| Virtual Displays | Allow Virtual Displays, Fixed Virtual Displays, Persistent. See Set virtual displays for a team. |
| Networking | Direct Connections Only, Connection Port Range, On Premise Relay Servers. See Choose a connectivity option, Network requirements, and On-premises relay servers. |
| Advanced protocol settings | RDP Enabled, VNC Enabled and their ports |
| Misc | Cloud Connection History, Local Configuration Changes, Send anonymous crash reports |

Some settings are labeled with a platform or a minimum Connect version (for example 10.5+).
Keep hosts awake#
Sleep Override (Connect 10.5 or later) is a setting that prevents Windows and Mac hosts from sleeping. A sleeping host cannot accept connections, so this setting keeps hosts available, for example overnight or while an AI agent works on them.
| Value | What it does |
|---|---|
| Follow System Settings (default) | The host sleeps according to its own power settings. |
| Always Keep Awake | The host does not sleep. |
| Keep Awake on AC Power | The host does not sleep while on AC power. On battery power, it follows its own power settings. |
Limit session length#
Max Session Duration (Connect 10.5 or later) is the maximum length of a Fluid session, in seconds. A session that reaches this length is disconnected. To apply no limit, leave the value at 0 (Not set, the default). For example, enter 3600 to end sessions after one hour. To disconnect idle sessions instead, set Idle Timeout.
Restrict who can sign in to hosts#
By default, any user with a local account on the host can sign in to the host with that account's username and password. On Windows, the account must also be a member of the Administrators or Users group and, with Connect 10.15.28 or later, must hold the Allow log on locally right; without that right, a correct password is still refused. Local Authentication Restrictions (Connect 10.5 or later) is a setting that limits local account sign-in to the users and groups you list. The restriction applies to every sign-in with a local account, whether the connection is routed through Jump's cloud or through Cloudless Fluid.
- While editing a configuration, under Fluid Settings, click Configure next to Local Authentication Restrictions.
- Select Restrict to allowed users and groups.
- Under Users and Groups, add names as they appear on the host. Click Save.
- Save the configuration.
A user matching either list can sign in; all other users are denied.
Warning
If restrictions are enabled and both lists are empty, no one can sign in with a local account.
| Host | Users | Groups |
|---|---|---|
| Windows | alice or DOMAIN\alice |
Remote Desktop Users |
| macOS | Short username, such as alice |
admin, staff |
| Linux Alpha | Local username, such as alice |
sudo, wheel |
Assign a configuration#
- On the Connect Configurations page, click Assign configuration next to the configuration.
- Select computers on the Computers tab, or groups on the Access Groups tab.
- Click Assign.
To assign a configuration from a computer's or Access Group's page, click the value next to Connect settings (Not assigned if no configuration is assigned). If a configuration is shown, click Assign. Choose a configuration and click Assign.
To stop enforcing a configuration, click Remove configuration next to it, select the computers or groups, and click Remove.
Edit, copy, or delete#
Use the buttons next to a configuration:
- Edit configuration: changes apply to every computer and Access Group the configuration is assigned to.
- Create Duplicate: creates an unassigned copy with " - Copy" appended to the name.
- Export to another team: copies the configuration without assignments to another team you administer.
- Delete configuration: removes the configuration from every computer and Access Group it is assigned to.
Which configuration applies#
- A computer or Access Group has at most one configuration. Assigning another configuration replaces the existing one.
- A configuration assigned directly to a computer overrides a configuration inherited from an Access Group.
- If a computer belongs to several Access Groups with different configurations, only one of those configurations applies, and you cannot control which one. The dashboard may show a configuration other than the one applied. Avoid this situation, or assign a configuration to the computer directly.
- A computer with no direct or group configuration uses the settings chosen in Connect on that computer.
Warning
If a computer with its own configuration is added to an Access Group that has a configuration, the computer's own assignment is removed and the computer inherits the group's configuration. If no other computer or Access Group uses the removed configuration, the removed configuration is deleted.
The Connect Settings column in Computers and a computer's Connect settings field show its configuration. An inherited configuration shows "(inherited from" followed by the group name. To change an inherited configuration, remove the computer from the group or assign a configuration to the computer directly.
Result#
- Online computers receive changes within about 20 seconds. Offline computers receive changes the next time Connect connects to Jump.
- Connect applies every value in the configuration, not only the values you changed. Connect is also set to start automatically.
- Unless the configuration enables Local Configuration Changes, Connect's Settings window shows Settings are managed by your team's administrator and most settings cannot be edited.
- When a configuration is removed or deleted, the computer reverts to the settings chosen in Connect on that computer.
Related#
- Control access with Access Groups
- Jump Desktop Connect settings: a description of each setting.
- Add and manage computers: select a configuration when you create an installer.