← Portal
πŸ’»

RM Workspace

Remote Worker Β· Tailscale access

Available computers tailnet Β· tail51536c.ts.net

Connect over Tailscale, then use Screen Sharing. Status shown from the last sync β€” just now. To make this live, wire it to the Tailscale API (see setup guide).

Connect from anywhere

πŸ”’
Install Tailscale & sign in

Tailscale puts your device on the private company network (an encrypted mesh). Once connected, the office computers above appear β€” screen-share into the one you need. Sign in with your Crawford & Co account.

Get Tailscale →

Getting started

1
Install Tailscale

Download from the button above and install it on your laptop. Sign in with your CC account (SSO).

2
Wait for approval

First time only β€” an admin approves your device before it can join the network. You'll be notified when you're in.

3
Pick a computer

Open the list at the top of this page. A green dot means it's online. Click Screen Share on the machine you need.

4
Work on that screen

All client work happens on the office machine β€” never save client files to your own laptop. Sign out of the machine when you finish.

⚠ Every shift
  • Make sure Tailscale is connected (the icon is green) before you try to reach a computer.
  • Keep all client work inside the screen-share β€” don't copy files, screenshots or client data onto your own device.
  • Only connect to the machine you've been assigned. If it's offline or you can't reach it, contact IT before starting.

Secure setup guide · IT / admin

πŸ”’ The principle β€” sensitive files stay on the UK machine

Remote workers do not get client files on their own devices. They use Tailscale to screen-share into a UK office computer and see only its screen β€” the files, email and client systems live on that machine and never travel to the worker's laptop. Tailscale builds a private, end-to-end encrypted link (WireGuard) directly between the two devices; nothing is exposed to the public internet. So an overseas worker can work on sensitive data without ever holding it.

1Set up the office machinesOffice
  • Install Tailscale on each UK machine that holds client data and sign in with the shared manager.ccltd@ admin account.
  • Enable Screen Sharing (macOS: System Settings β†’ General β†’ Sharing) or Remote Desktop (Windows).
  • Set it to never sleep when the display is off, and in the Tailscale admin console disable key expiry for these machines so they stay reachable.
  • Tag them tag:office so ACLs can target them as a group.
2Onboard the remote worker's deviceAdmin console
  • Worker installs Tailscale and signs in with their CC account (SSO) β€” this ties the device to a named person.
  • Turn on device approval so no device joins the tailnet until an admin approves it.
  • Tag the worker's device tag:remote and keep key expiry ON (forces periodic re-auth).
3Least-privilege access with ACLsTailscale ACL
  • Remote workers should reach only the office access machine, and only on the screen-share port β€” not each other, not everything.
"acls": [
  {
    "action": "accept",
    "src":    ["tag:remote"],
    "dst":    ["tag:office:5900", "tag:office:3389"]
  }
]
// 5900 = macOS Screen Sharing Β· 3389 = Windows RDP
// no other rule for tag:remote = everything else is denied
4Keep the data on the machineSession
  • Screen-share is pixels only β€” nothing transfers by default. In the Screen Sharing / RDP settings, turn off clipboard sharing, file transfer and drive redirect for zero copy-out.
  • Disable Taildrop (Tailscale file-send) for tag:remote so files can't be pushed between devices.
  • Client files therefore never leave the UK office machine.
5Identity, audit & offboardOngoing
  • Enforce MFA at the identity provider (the SSO that signs people into Tailscale).
  • Turn on audit logging (and Tailscale SSH session recording if you use tailscale ssh) so every connection is traceable.
  • Off-boarding = remove the person's device in the Tailscale admin console β†’ access is cut instantly; then disable their CC account.
  • Optional β€” UK exit node: if a worker must also browse client web systems as UK, route their traffic through a UK machine set as an exit node.

Hard controls checklist

βœ“
Device approval onno device joins unapproved
βœ“
ACLs least-privilegetag:remote β†’ office only
βœ“
Screen-share onlyports 5900 / 3389
βœ“
Clipboard / file xfer offzero copy-out
βœ“
Taildrop off for remoteno file send
βœ“
SSO + MFAnamed, verified sign-in
βœ“
Key expiry on (users)periodic re-auth
βœ“
Audit logging onevery connection traced

Remote team

0 online
0 total
WorkerRegionAccessStatus

Sample roster β€” wire to live Tailscale device presence once each worker's device is enrolled.