Skip to content

Set up Jump Desktop for an organization#

Deploy Jump Desktop for Teams in the following order, and follow each link for details. This order avoids rework because computers receive their access and settings when Connect is installed. Use it when an IT administrator deploys remote access across a company, or when the most technical person in a small office configures a team for colleagues.

For a small team that does not require company sign-in or managed settings, Get started with Jump Desktop for Teams provides a shorter procedure.

Before you start#

  • A Jump Desktop account for the administrator. Sign in to the Teams dashboard.
  • The list of people who need access and the computers they connect to.

Steps#

A team administrator performs every step.

  1. Choose a plan. Single sign-on, SCIM, and Connect Configurations require Jump Desktop for Teams Enterprise; Access Groups are available starting with Pro.
  2. Create the team. Get started with Jump Desktop for Teams: create the team, then add at least one more administrator (Team roles and remote access).

  3. Configure sign-in (Enterprise). Subscribe first: trials cannot configure single sign-on, and SCIM and domain verification require it.

    If you do not use SSO, require 2-factor authentication instead (Pro or Enterprise). For details, see Security best practices. 4. Check the network. Network requirements lists the host names and ports to allow. If connections must stay on your network, see Choose a connectivity option. 5. Plan access. Control access with Access Groups: group users and computers so each person can access only the computers they need. 6. Configure Connect (Enterprise). Use Configure computers with Connect Configurations to enforce settings; Jump Desktop Connect settings describes each setting. 7. Deploy Connect to hosts. Create a pre-configured installer with the Access Groups from step 5 and, on Enterprise, the Connect Configuration from step 6. Every computer the installer sets up receives them. Then deploy the installer: - Deploy Connect to many computers with a script or deployment tool. Linux hosts Alpha use the standard installer with a Connect Code instead. - Deploy Connect with Microsoft Intune to Windows hosts. - On Mac hosts, Grant macOS permissions to Connect lists every permission Connect requires. 8. Invite users. Add and manage users, or allow SSO and SCIM to add them. Send users Join your team and connect. 9. Review security and monitor. Apply Security best practices, then review Activity Logs and Connection Logs. To archive logs or automate team management, use the REST API.

Check that it worked#

  • Your hosts are listed in the team's Computers.
  • Invited users are listed in Users and can view and connect to their computers.
  • Connection Logs record their connections.

Next steps#