Tailscale
June's sandbox joins your tailnet as a device under your identity, so June can reach your private services and machines.
Connect Tailscale and June's sandbox joins your tailnet as one of your devices, so June can reach what you reach there: a document server, a NAS, a remote machine over SSH. Give June the device name, service address and what you want it to check; connecting alone does not tell it which service to use.
TailscaleFull access to your tailnet
The device June adds runs under your own Tailscale identity, so it can reach every device your account can. Connect it only if you want June to have that reach.
Check whether the backup job on my NAS ran last night.
Find the lease agreement in my Paperless and tell me the notice period.
What June can do
From its sandbox, June reaches the devices and services on your tailnet that your account reaches, as one more of your devices: it can open a private web app, call a service’s API or reach a machine over SSH. Joining the tailnet gives June a network route; a service may still need its own login, key or SSH credentials. What June can change there depends on the access those services and machines grant it.
What June does not do
- It joins your tailnet only from your own chats and projects, never from a schedule or an organization's chats (why).
- It does not change your tailnet's settings or access rules.
The device shows up in your Tailscale admin console. Disconnect in June removes the device identity June stored, so new sandboxes stop joining; also remove the device in the Tailscale admin console.
ownCloud and Nextcloud
June reads documents from your ownCloud or Nextcloud server, saves the files it writes back to it, and moves, renames and deletes files there, over WebDAV.
X
June reads posts, mentions, bookmarks and threads from your X account, and posts, replies, reposts, likes, bookmarks and follows when you approve each one.