JUMP-TEAMS · FOR BUSINESS
Give your people a proper Windows workspace, wherever they work. Bring cloud PCs, access and everyday administration together — without becoming an IT expert.
For a small business, the useful starting point is a recurring role. In fictional Harbour Operations, Sam keeps quotation, costing and proposal tools together, while Jules works in a separate development environment with a chosen editor, Git, runtime and repository. The business installs and licenses those applications and confirms the real workflow before expanding.
Choose Months when a role needs the environment repeatedly across the billing period and the complete cost makes sense. Months is the full monthly price with up to 300 uptime hours per desktop; it is not prorated to a few working days or a pooled Team allowance. Hours combines running compute with retained service charges, including when stopped. Monthly subscriptions and eligible Hours prepaid funding remain separate.
Use one desktop for each simultaneous Windows user. Assign Team roles, Windows Standard or Administrator access, application permissions and billing responsibilities deliberately. A member count is not a count of paid desktops, and assigning a desktop is not the same as granting every application permission.
Before adding the next person, use the DaaS fit checklist, calculate a three- or five-desktop budget and agree a contractor handover process. These guides make the access and recurring-cost decisions concrete.
Jump-Teams adds shared administration to Jump-Desk Windows 11 Pro cloud PCs. A business owner can create a Team, invite colleagues, assign desktops and delegate selected permissions. Choose a suitable plan and region for each desktop, then configure each person’s separate Windows access.
Name it and confirm the currency.
Choose each colleague’s role and additional permissions.
Choose a Jump-Desk plan, region and performance for the work.
Configure the login and test the member’s connection.
YOUR NEXT STEP
Invite colleagues as Admin or Member, assign desktops and review the permissions needed for their work. Team roles, Windows access and funding permissions are separate decisions for the owner.
Explore Jump-Teams
01 / JUMP-TEAMS
The next hire needs a Windows application. A contractor joins for a project. Your operations colleague works from another city. Jump-Teams gives these requirements one place in the product, with people and their assigned cloud PCs visible together.
Start with the team you have today. Choose a desktop configuration that matches the role, test the required application and add the next workspace when the work calls for it.
02 / JUMP-TEAMS
The person who creates the Team is its Owner. Invite colleagues as Admins or Members, then choose additional permissions for the tasks they need to perform. An appropriate colleague can help with administration without every team member receiving the same controls.
Keep billing access deliberate. Team roles govern what someone can do in Jump-IT; Windows login access is configured separately. Your application accounts and licences also remain part of the setup.
03 / JUMP-TEAMS
For regular work, start by assessing Months. Each monthly desktop includes up to 300 hours of uptime and uses subscription checkout. The retained workspace keeps compatible apps, settings and working files between sessions.
Compare that uptime allowance with the real working pattern. A session that has been disconnected can leave the desktop running, so make checking usage and desktop state part of the routine.
04 / JUMP-TEAMS
An intermittent development task, a short freelance project or a clean Windows test environment can suit eligible prepaid Hours desktops. Review central Team funding or member self-funding where offered. Personal self-funding requires the member’s explicit approval.
Hours compute is charged while running. A separate service charge continues while the desktop is retained, including when compute is stopped. Review both parts of the cost before choosing it.
05 / JUMP-TEAMS
A new starter: invite the colleague, choose their permissions and assign a suitable desktop. A growing operation: share the permitted administration with a trusted colleague. A distributed team: choose an available region around the person and workload.
A project ending: save required files, review Windows access and Team membership, then decide what happens to the desktop and its billing. Each is a separate decision, so a clean handover needs all of them.
06 / JUMP-TEAMS
Choose one real role and a representative application. Test the supported device, network, sign-in and file workflow. Record what worked before extending the arrangement to other staff.
Jump-Teams offers the administration shown here. If your organisation needs centrally enforced device policies, custom images, single sign-on integrations or specialist compliance controls, assess those requirements explicitly before adopting any service.
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.
Owners and operators who need to coordinate Windows cloud desktops for a small or medium business, with invitations, assignments and selected shared administration.
Yes. Choose Admin or Member roles and additional permissions. The Team creator is Owner. Check payment-related permissions separately.
No. Team membership and Windows desktop access are separate. Configure and test both during onboarding.
Months uses subscription checkout. Eligible Hours desktops use prepaid funding and have their own funding requirements.
Use appropriate separate Windows access. Team membership does not imply shared credentials or simultaneous multi-user Windows licensing.
Start with a representative role, choose the right desktop and give each person a clear way to begin.
Use the GPT-6.1 Terra and Windows execution guide to plan a small development team’s build-and-review process. It separates AI tool permissions, Team management, Windows privileges and the evidence needed before a project is handed over.
Compare a touchscreen MacBook Pro with local Apple-silicon AI work and a Surface Laptop Ultra with a compatible local CUDA workflow. Both guides show how Jump-Teams organises separate Windows desktops for colleagues while the lead’s machine handles its own tasks. Neither local GPU is shared with the team’s cloud desktops.
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 →
