JUMP-TEAMS · THE OWNER’S ONBOARDING GUIDE
Turn the next hire, contractor or remote colleague into a clear set of decisions — with a Windows workspace ready for their actual role.
To onboard with Jump-Teams, create the Team, invite the colleague, choose their Team permissions and assign a suitable Jump-Desk. Configure Windows access separately, confirm the funding arrangement and test the connection on the person’s device before their first working session.
List required applications, licences, files, expected uptime and the person’s main working location. Include any specialist devices or restrictions.
Open Active Team and choose Create Team. Give it a recognisable name and confirm the currency before creating it. The creator becomes Owner.
Open Members, choose Invite member and use the email address the colleague will use to join. Select Member or Admin and only the additional permissions needed.
Have the colleague accept the invitation with their own account. Verify the correct Team appears before assigning the operational work.
Select a suitable available region, tier and plan. Review the price, uptime and funding requirements. Assign the Jump-Desk to the intended colleague.
Set up the separate Windows login and permissions for the desktop. Team membership by itself is not the Windows credential.
Ask the colleague to connect using a supported client, open the required application and complete a representative task. Confirm file and backup arrangements.
Record who handles administration, funding and support. Set a date to review usage and whether the workspace still fits the role.
YOUR NEXT STEP
Send an invitation, assign the right desktop and confirm that the colleague can connect with their own Windows credentials. Test the actual application and file workflow before calling onboarding complete.
Explore Jump-Teams
01 / JUMP-TEAMS
Decide who needs to invite people, manage assignments, review usage or handle payment settings. Give each responsibility to an appropriate person and use the controls available in the product.
A new administrator does not automatically need control of billing. An employee who only needs to do their work should not receive extra management permissions by default.
02 / JUMP-TEAMS
Months uses subscription checkout and includes up to 300 hours of desktop uptime each month. Confirm that allowance matches the role, including time a disconnected desktop may keep running.
For eligible Hours desktops, review central funding and any member self-funding choice. Member funding needs their explicit approval, and personal payment details stay private. Explain that the service charge continues while the Hours desktop is retained.
03 / JUMP-TEAMS
Test the colleague’s actual device and network. Check client installation, display scaling, keyboard behaviour and how they will obtain support. Install only appropriately licensed, compatible applications.
Keep a short internal record of the setup. Store credentials through your organisation’s normal secure process, rather than including them in general onboarding notes or sending shared logins around the team.
04 / JUMP-TEAMS
First preserve the business files and results you need. Review application access and the person’s Windows access. Then review Team membership and the desktop’s ongoing funding or subscription.
Removing membership, stopping compute and deleting a desktop are different actions. Do not assume one completes the others. Check the outcome in the product and save required work before destructive desktop actions.
05 / JUMP-TEAMS
After the first successful setup, reuse the role checklist for the next person. Keep the requirements current as the applications, team and working pattern change.
For a business with more specialised identity, policy or regulatory needs, check those requirements separately. A clear onboarding process is useful even when additional management tools are required.
INSIDE THE PRODUCT
Watch the current interface with demonstration data. Each recording has playback controls, captions and a written walkthrough.
Create a Team, confirm its currency, and invite a colleague with the appropriate role.
Choose a Team, plan and responsible person, then set separate Windows access before checkout.
Review a Team desktop, change its responsible member, and find the member’s Windows connection.
Start with a role the business needs to support. For a contract developer, prepare a Windows desktop with the selected editor, Git, runtime, project repository and test accounts, then rehearse building the application and handing over a code change. For an operations colleague, prepare the licensed business applications and project folders used through the day. Choose capacity and access for that work, and check the actual device and connection.
Include the desktop plan, retained-desktop service charges on Hours, software subscriptions and the support needed to keep work moving. For prepaid funding, decide who can fund a wallet and review the remaining balance before a busy period. Use the account’s live prices.
Keep the person’s Jump-IT account, Team role and Windows credentials separate. Confirm the member can reach only the controls they need. When a role changes, review Team permissions, Windows access and application accounts together; removing membership alone is not a complete offboarding process.
A subscription for regular work, with up to 300 hours of uptime per desktop each month. Review the allowance and stop desktops when work finishes.
Eligible desktops draw on prepaid funding. Compute is charged while running, plus a separate service charge while retained. Team wallet and eligible member-approved personal funding have separate permissions.
Consider an annual commitment for an ongoing role. Check the live terms, expected software lifespan and likely team changes before choosing.
Confirm their email address, role, required permissions, application needs, expected uptime and funding arrangement.
Available actions depend on the person’s role and additional permissions. Review the controls shown in the product instead of assuming the role name grants every permission.
Treat Team membership, Windows access and billing as separate decisions. Review each explicitly during offboarding.
A complete rehearsal of the colleague’s role: for example, a developer builds the customer portal, checks it in a Windows browser, commits the change and hands over setup instructions. Prepare the required tools and approved project access, then check reconnecting from the colleague’s normal device and network.
Start with a representative role, choose the right desktop and give each person a clear way to begin.
Our touchscreen MacBook Pro and Surface Laptop Ultra guides compare current hardware without requiring every colleague to buy the lead’s device. Choose separate Windows desktops for simultaneous work, test each worker’s connection and check regional requirements. Team management, Windows privileges, application permissions and funding remain separate decisions.
Related device guidance added 31 October 2026.
TEAMS GUIDES
BUSINESS GUIDE
Evaluate DaaS for a small team: Windows applications, Jump-Teams access, monthly desktop budgets, practical checks and when another setup fits better.
Read the guide →BUSINESS GUIDE
Budget three or five monthly Windows cloud PCs. Compare Months with running and retained Hours costs, software licences, access and renewal checks.
Read the guide →BUSINESS GUIDE
Plan a contractor’s Windows workspace from setup to handover: Team roles, Windows privileges, project files, application access and monthly cost review.
Read the guide →PRODUCT VIDEO
Watch the Jump-Teams demo: create a Team, invite a colleague, connect to Windows and add a second regional cloud PC with separate access permissions.
Watch the walkthrough →PRODUCT VIDEO
Watch a first-member onboarding demo: create a Jump-Team, choose permissions, send an invitation and hand over a Windows cloud PC with individual access.
Watch the walkthrough →PRODUCT VIDEO
Watch a Team member accept an invitation, find their Jump-Desk, review connection settings and open Windows with their own account and connection file.
Watch the walkthrough →PRODUCT VIDEO
See a regional Windows cloud PC added to Jump-Teams: choose Virginia, a monthly plan and separate Windows privileges for a colleague and deputy.
Watch the walkthrough →STARTUP GUIDE
Built by a startup, for startups. Give your team Windows cloud PCs on supported devices you already own, with invitations, access controls and flexible funding.
Read the guide →
