Joining and access
How devices join a workspace, what tokens are, and what each access level can do.
Ways to join
There are several ways for a device to get into a workspace. Pick one based on the machine.
| Way | Good for | How |
|---|---|---|
| Install command | New machines, servers without a desktop, several at once | On the host, Devices → Add device → Create token, then run the command on that machine |
| Join link | Sending in a chat app such as Slack or WeChat | The other person opens it, clicks Open with danio and confirms joining |
| Local network + join password | Computers in the office | Join a workspace → Local network, choose the workspace and enter the password |
| Local network + approval | Computers in the office, when the host has no password | Choose the workspace and click Ask to join, then click Approve on the host's Devices page |
| Token | Machines that already have danio installed | Join a workspace → Token, enter the host address and the token |
- To be found on the local network, the host must have Local discovery on, and both firewalls must allow UDP 7420. If the computers are on different subnets, use Find by address on the same page.
- By default the host has no join password, so every local network join needs approval. To set one, fill in Join password under Workspace details → Connection.
- A request expires if nobody handles it within 10 minutes.
- For devices that join over the local network, access and whether they accept renders follow Access after joining and Render after joining under Connection. The defaults are "Workstation" and not accepting renders.
Tokens
A token is a credential a device uses to connect to the host. It carries an access level.
When a device joins with an install command or a join link, the token is in the command or link. When it joins over the local network, the host sends the token to the device automatically.
- Single: works only for the first machine that joins with it. Copied to another machine, it doesn't work. Revoking it disconnects that device immediately.
- Multiple devices: until revoked, any new machine can join with it. Good for starting several cloud servers at once. Revoking it only prevents new machines from joining; devices that have already joined remain connected and keep working.
- Integration tokens: for scripts on other computers or other systems calling the host's API. Create them under Workspace details → Plugins and integrations (see HTTP API).
Device tokens are under Devices → Tokens. Each shows when it was last used. Hold Revoke for 2 seconds. A single-device token disconnects that machine right away; a multi-device token keeps existing devices connected while rejecting any new device. Install command opens the command created back then, so you don't need a new one when you start more servers a few days later.
A token appears in plain text in the command and stays in that machine's command history. If you suspect it has leaked, revoke it and add the device again.
Access
Access is what each device can do in the workspace. There are four levels, and each level includes everything the level below it can do.
| Level | What it can do | Usually for |
|---|---|---|
| None | Can't see projects or tasks; only renders the chunks given to it | Render machines, rented servers |
| Viewer | Views projects, tasks, progress, previews, devices and usage; downloads films and fragments | Producers, directors |
| Workstation | Submits and updates tasks, controls the tasks it submitted; creates and edits projects | Artists' computers |
| Admin | Controls everyone's tasks; manages devices, the store, resource packs, cleanup, plugins and workspace settings | The host, the person in charge |
The device that creates the workspace is "Admin", and the host itself is always "Admin".
Rendering isn't controlled by access: every device can render, and whether it does is decided by its Render switch. So "None" is enough for a machine that only renders. It picks up chunks and hands in results without seeing your projects.
- Change access under Overview → Access and rendering in the device details. It takes effect right away.
- Choose it when you add the device. For render servers, choose None.
- Devices with "None" access can still read and write the store, because rendering needs it. Put machines you don't trust in a separate workspace with a separate store.