How to set up remote IT support for a small team

• One owner account for the business's PCs, protected with two-step verification. Don't share it: teammates get their own accounts and join your team.
• Who supports what. List your helpers and, for each, the PCs and servers they look after and what they may do there.
• Attended or unattended, per PC. PCs people sit at usually stay attended (they click Allow). Unattended access is for PCs you're responsible for, with the agreement of the people who use them.
• The plan. The free plan covers up to 5 PCs and 5 saved hosts for business use, which can be enough when one person does all the support. Teams, roles and the audit log are part of Pro, and everyone in a team needs Pro.

1. 1

   Step 1: Protect the owner account

   Sign in on the website, open Dashboard, then Security, and turn on Two-factor authentication. Save the 10 backup codes somewhere safe. Ask everyone who'll join the team to do the same on their own account.

2. 2

   Step 2: Add each PC to the account

   On each PC, run the installer from the download page and choose Set up this PC, or type a 6-digit code from Add a PC on your dashboard. It installs without administrator rights; IT can install it for every user of a PC with /ALLUSERS.

3. 3

   Step 3: Start a team and invite people

   Open Teams in the app, or Team on the website dashboard, and click Start a team. Invite each helper by email. They get an email and accept with one click, or accept it on their dashboard. The invite works for 7 days and only for the RemoteAccessApp account with that email. You can also copy the invite link and send it over chat.

4. 4

   Step 4: Give each person a role and their PCs

   Choose a role for each person, pick the PCs and saved hosts they get, set what they may do on each PC, and click Save access. Shared PCs appear on their Devices page. With lots of PCs, the teams and roles help article explains access rules, which give someone every PC with a tag at once.

5. 5

   Step 5: Decide how each PC lets people in

   Sharing a PC never turns on unattended access: by default the person at the PC clicks Allow for each session. For a PC nobody sits at, someone at that PC turns on Unattended access from the RemoteAccessApp tray icon, and allows each helper's console once with Let this console connect without asking next time ticked.

6. 6

   Step 6: Check the audit log

   Open the team's Audit log now and then. It lists sessions on the team's PCs, management jobs, invites, and role and permission changes, with filters and a CSV or JSON download. Custom roles and the team activity log are among the releases in what's new in RemoteAccessApp: October 2026.

ProEvery team has an Owner, the person who started it. The built-in roles cover most small teams, and you can make custom roles too:

• Admin: invites people, manages their access to the PCs the Admin manages, and sees the audit log. Admins never give more than they have.
• Technician: hands-on support on the PCs shared with them, and sees the audit log.
• Member: uses the PCs shared with them, with the permissions you set.
• Viewer: can only watch, and never controls a PC. Useful for training.

On each PC, for each person, you choose from these permissions:

The server signs the permissions into each connection, and the PC enforces them. There's more on deciding who gets what in access control for PCs and servers.

• Trusted networks. Limit a PC to connections from your office's network: on the Devices page, right-click it and choose Restrict by IP…. You can limit the whole account to trusted networks in the app's Settings too.
• A connection password on a sensitive PC: anyone connecting has to type it first. It's set at the PC, and our servers never see it.
• Review trusted consoles. At each unattended PC, the tray menu's Trusted consoles and browsers… lists who gets in without asking. Remove anyone who has left; it takes effect at once.
• Keep notes. PC history lets you keep notes on each PC, and your account's activity log covers up to 90 days, downloadable as CSV or JSON.

For the rest of the basics, from two-step verification to old PCs you no longer use, work through how to keep your remote access safe in 2026.

Your helpers open a shared PC from their Console or a browser, and the person at the PC sees the Allow prompt with who is connecting. During the session there's chat, a command prompt and Windows tools, as their permissions allow. For the same fix on many PCs, see how to run a script on many PCs at once. The small business IT support page has the bigger picture, and how to manage multiple computers from one place covers keeping the whole list in order.

Wondering what this looks like day to day? Read a week of remote IT help for a five-person office: a new laptop, a stuck printer, updates, a file from home and a Friday tidy-up.