Skip to content

Teams and management

Manage remote access for a whole team

One address book everyone can use, rules that hold on every computer, and a way to install RFDesk on many machines without visiting each one. Teams turn a personal tool into something an organisation can run.

  • Owner, admin and member roles
  • Policies lock settings on or off
  • Silent install that joins the team by itself

People and roles

Create a team from your account and invite colleagues by email address. The invitation appears for that account when they sign in, and you also get a one-time code you can pass on yourself. There are three roles. The owner can do everything, an admin manages members, devices and the address book, and a member uses them.

A shared address book

A team has an address book of devices with a name, the RFDesk ID and notes, sorted into folders and tags. It appears on the connect page beside your own. Passwords are never stored in it, and the owner can decide whether members may edit it.

Computers that belong to the team

A computer joins when its user signs in on it and chooses Add this computer to my account, then assigns it to the team. Members see it in their device list. The owner and admins can rename it, set its access rules and wake it over the network. Computers can be sorted into device groups, and a group can lock rules of its own.

Policies that hold everywhere

A policy is a set of rules that RFDesk on each enrolled computer has to follow. Each rule is Locked on, Locked off or Not set, and a locked rule cannot be changed at the computer.

  • What a visitor may do: control, file transfer, the file manager, clipboard, sound, voice calls, remote printing, the whiteboard, restart, privacy mode and recording.
  • Whether unattended access is possible at all, and whether visitors must be signed in.
  • What happens when a session ends: lock the computer, or turn its screen off.
  • Limits: end a session after a number of minutes without input, and how many visitors may be connected at once.

Rollout without a visit

An enrolment key lets RFDesk join the team by itself when it is installed. Make a key, optionally with an expiry, a limit on how many computers may use it and a folder for the new machines, then run the silent install command it gives you, or hand it to your deployment tool. Nothing is shown on screen. RFDesk installs, starts at sign-in and joins the team.

A help page and a view of the work

A team can switch on a public help page with its own link, where customers queue for support without an account. Usage reports show sessions with the team's computers by period, by computer and by the person who connected.

Good to know

  • A policy applies to computers enrolled in the team, not to computers that only appear in the address book.
  • A team can make things stricter than the server's own rules, never looser.
  • An enrolment key is shown only once. Anyone who has it can add computers, so keep it private and revoke it if it is lost.
  • The silent install command is for the Windows installer.

FAQ

Questions and answers

Can a team stop its computers being reached unattended?

Yes. A policy can lock unattended access off, which also switches off access for other people on those computers.

When does a changed policy take effect?

Computers that are online get it at once, the others when they next come online. A session that is already running keeps what it started with, except that anything now forbidden is switched off.

Does inviting someone send them an email?

No email is sent. The invitation appears for that account when they sign in, and you receive a code you can pass on yourself. The code works once, for 14 days.

Can members change the shared address book?

That is a team setting. With Members can edit the address book switched off, only the owner and admins can add, change or remove entries.

Ready when you are

Connect from this browser now, or get the app for the computer you want to reach.