Set up the client
Create a workspace for the client and add your technicians as operators.
One workspace per client, one log per workspace.
Give each client its own workspace, roles and approval rules. Your technicians help users from a browser, and each client’s audit log exports on its own.
Where it fits.
- Separation by designAnything in a workspace you are not a member of answers as not found, and links across workspaces are refused. One exception: Anslation’s platform owner account can open any workspace as an owner, and every step it takes there is written to that workspace’s audit log.
- Rules per clientEach workspace has its own policies, so one client can require admin approval while another asks the user.
- Evidence per clientExport one client’s audit log as CSV when they ask what happened.
How a session runs for you.
Three steps from a request to a solved problem, with the person in charge of their own screen.
Set its policy
Choose who approves sessions for that client.
Help their users
Stage a session in their workspace, share the code and guide the user.
Good for, and not for.
Good for
- Attended help for client users
- Clients who want evidence of every session
- Keeping each technician to the right client
Not a fit for
- RMM work: patching, monitoring and fleet scripts
- Unattended screen access to client servers
- File transfer to client computers
Settings to start with.
A starting point, not a rule: every setting can change per workspace.
| Setting | Suggested | Why |
|---|---|---|
| Workspaces | One per client | Nothing crosses from one client to another |
| Approval | Admin or manager approval | A second person signs off client sessions |
| Roles | Technicians as operators, client contacts as auditors | Clients can read their own log |
Read next.
- IT help desksA queue with SLA timers.
- Customer supportScreen sharing for customers, with no app.
- All use casesFive kinds of team, one way to help.
- ComparisonsSide by side with AnyDesk, TeamViewer and seven more tools.
- SecurityCodes, consent, roles and the audit log, and what is not done yet.
- Screen share checkTest a browser and a network before a session.
- Anslation RemoteThe product, what it does and what it does not.
Your questions, answered.
Is Anslation Remote an RMM?
No. It is remote support with a view-only screen share, a queue and an audit log. It has no patching or monitoring; its optional agent only reports a device’s status and runs approved terminal commands.
Can technicians see other clients’ sessions?
Only in workspaces they are members of. Everything else answers as not found, except to Anslation’s platform owner account, whose every step in a workspace is written to its audit log.
Can a client get a copy of their session history?
Yes. Export the client workspace’s audit log as CSV, filtered by date or session.
Bring browser support to your team.
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