Give roles
Owners and admins run the workspace, operators run sessions, auditors read the log. Keep admins few.
Anslation Remote
A remote support checklist for help desks and small teams.
What to decide before your first session, what to check in each one, and what to review afterwards, with the matching Anslation Remote setting where there is one.
In short
What should an IT help desk set up for remote support?
Decide who may start, approve and audit sessions; set an approval rule for each kind of device; agree how codes are passed on; run requests through a queue with response targets; test networks before the first session; and review the audit log on a schedule. Tell the people you help how real support contacts them, so a scam call stands out.
Set up in six steps.
Set approval rules
Per policy: ask the person you help, an admin, a second approver, or approve by policy for low-risk help.
Agree on codes
Codes go only to the person who asked for help, by the channel they used. Each works once, for 15 minutes.
Run a queue
Requests get a priority, an owner and an SLA timer: by default 1, 4, 8 or 24 hours, from urgent to low.
Test the network
Run the screen share check on a typical office computer. If the direct path fails, plan a TURN relay.
Review the log
Filter the audit log by outcome and severity on a schedule, and export it as CSV when you need to.
The checklist and its settings.
| Item | In Anslation Remote | Why it matters |
|---|---|---|
| Who may start a session | The operator role or above | Sessions start only from people you named |
| Who approves | The policy’s approval mode | Sensitive devices get a second pair of eyes |
| Terminal commands | Blocked or allowed per policy; an admin approves a terminal session with someone at the device | A command can do anything the agent’s account can |
| Response targets | SLA defaults of 1, 4, 8 and 24 hours by priority | No request waits unseen |
| Evidence | The audit log, its CSV export of up to 10,000 rows, and reports over 24 hours, 7 days or 30 days | You can show what happened and when |
| Separate teams or clients | One workspace each | Members see only the workspaces they belong to |
What this covers, and what it does not.
Anslation Remote covers
- Browser screen sharing with consent
- Chat and pointer notes
- Approvals, a support queue and an audit log
- Terminal commands on managed devices, with the optional agent
Plan another tool for
- Keyboard and mouse control: screen sessions are view-only
- Seeing a screen with nobody at the computer: screens are attended
- Moving files outside a live session: files go only while someone shares, accepted first
- Patching and monitoring fleets of devices (RMM)
Tell the people you help.
- How you contact themSay which channels your help desk uses, so a call from anywhere else stands out.
- What you will not ask forYour team does not ask for passwords, OTPs or payments during a session.
- How to stopThey can stop sharing or leave at any time, and the browser shows them while they share.
Read next.
- Remote for IT help desksA queue, SLA timers and a screen share from the employee’s browser.
- All guidesScreen sharing and remote support, answered plainly.
- Screen share checkTest a browser and a network before a session.
- Use casesHow help desks, support teams, schools and MSPs run sessions.
- ComparisonsSide by side with AnyDesk, TeamViewer and seven more tools.
- Anslation RemoteThe product, what it does and what it does not.
Checklist questions, answered.
What should be in a remote support policy?
Who may start, approve and audit sessions; which devices allow terminal commands; how codes are passed on; response targets by priority; and how often the audit log is reviewed.
Does a small business need a support queue?
Not at first. Staging sessions straight from the console works for a few people; add the queue once requests need owners and response targets.
Can we make sure operators do not approve their own sessions?
Yes. Set the policy to manager approval: an admin or owner other than the operator who started the session must approve it.
How do we show what happened in a session?
Each join, consent, approval and close writes an entry in the audit log, and chat and pointer notes stay with the session. Filter the log and export it as CSV, up to 10,000 rows at a time.
Remote support ke liye kya chahiye?
For the person you help, a desktop browser and the code. For your team, roles, an approval rule per policy, and a network that allows a direct WebRTC path or a TURN relay.
Keep reading
- Remote for IT help desksRun IT help desk remote support from a queue: SLA timers, assignment, a screen share from the employee’s browser, approvals and an audit log.
- Remote for small businessHelp staff and customers from a browser: one-time codes, consent, view-only screen sharing and an audit log, in a workspace you own.
- Share your screen safelyA short checklist for a screen share with IT support: who asked, what to share, what to close, and which private details stay off screen while someone watches.
- Remote securityHow one-time codes, consent, roles, workspaces, peer-to-peer media and the audit log work in Anslation Remote, and what it does not do yet.
Help people without asking them to install anything.
Tell us about your team and how you help people today. We read every request and reply by email.
Office hours: Monday to Saturday, 10:00–18:00 IST+91 74158 85838