Anonymous Mass Rollout

With an anonymous mass rollout you can install and activate the sensor on many machines at once. Your users do not have to do anything: no login, no "Activate" button, no partner selection. The sensor starts by itself and immediately reports data — anonymously, without any personal identity attached.

This is the fastest way to bring a whole company online, and it is a good fit whenever you only need occupancy data and not per-person data.

How it works in one picture

The sensor gets its identity from a small file called config.json. This file is created for your account and is signed by the Shigoto Hub. You place it on the machine, install the sensor silently, and the sensor picks the file up on its first start — it is then already activated.

Because the file contains no user id, the sensor runs in anonymous mode: it belongs to your account, but not to a named person.

config.json (account, no user)   +   silent installation   =   activated, anonymous sensor

What "anonymous" means here

Data is reported for the account, not for an individual. No user name, no user id and no personal identity is transmitted. See Security & Data Privacy for the details.

Before you start

• Requirements reviewed — see Requirements
• You know your BASE_URL — the address of the Shigoto Hub your sensors talk to (for example https://hub.example.com). Ask your partner for it if you are not sure. Everything on this page is relative to that address.
• You have access to the Admin Panel (or an API key) for your account
• You have a software distribution tool (Intune, Jamf, Munki, a login script, …)

Use the right BASE_URL

The config.json contains the server address the sensor will talk to. If you download it from the wrong host, your sensors will report to the wrong place. Always use the BASE_URL your partner gave you.

Step 1 — Download the sensor

Interactive: open BASE_URL/Download.html in a browser and pick your platform.

Via API / script: call BASE_URL/download?os=<platform>.

os= value	You get	Use it for
win	Windows installer (.exe)	Windows, manual or script rollout
intunewin	.intunewin package	Microsoft Intune
mac	macOS installer (.pkg)	macOS, standard rollout
macos-app	macOS app bundle (.app.zip)	macOS, copy-the-app rollout

The downloaded file is named after your product variant (for example ShigotoSetup.exe or desk.ly-Connect.exe).

Step 2 — Download the activation file (config.json)

This is the file that activates the sensor. Download it once and reuse the same file for every machine.

Interactive (Admin Panel)

1. Open BASE_URL/admin-panel using the command in your Sensor app. If you don't see admin section in Sensor app, ask your partner for leveling you up as an administrator.
2. Find your account (your customer name) and open it.
3. Switch to the Credentials tab.
4. In the Config generator card, leave the user field empty. This is the whole trick: no user id means anonymous.
5. Click Generate sensor config.
6. Download the result and save it as config.json.

Leave the user field empty

If you pick a user here, every machine that receives the file would report as that one person. For a mass rollout the field must stay empty.

Via API

curl -H "API-KEY: <your-api-key>" "BASE_URL/auth/config" -o config.json

No parameters are required for anonymous operation — the account is taken from your API key. Save the response body to a file named config.json.

API keys are created in the Admin Panel on the same Credentials tab.

Step 3 — Roll out

Install per user, not per machine

warning

Install the sensor per user, not machine-wide.

A per-user installation lives in the user's own profile, so the sensor can update itself silently in the background. A machine-wide installation needs administrator rights for every automatic update, which means your users would get a UAC prompt again and again — or updates would simply fail.

The Windows installer is a per-user installer by default; just don't run it as a different (administrative) user.

3a — Place config.json in the user's profile

Copy the file you created in step 2 into the user's configuration folder. The folder is always named Shigoto, never after the partner product — it is shared by all white-label builds on the machine.

Windows

%APPDATA%\Shigoto\config.json

which resolves to

C:\Users\<username>\AppData\Roaming\Shigoto\config.json

macOS

~/Library/Application Support/Shigoto/config.json

which resolves to

/Users/<username>/Library/Application Support/Shigoto/config.json

Create the Shigoto folder if it does not exist yet, and make sure the file belongs to the user and is readable by them. Example for Windows PowerShell, running in the user's own context:

$dir = "$env:APPDATA\Shigoto"
New-Item -ItemType Directory -Force -Path $dir | Out-Null
Copy-Item "$PSScriptRoot\config.json" "$dir\config.json" -Force

Example for macOS, running in the user's own context:

dir="$HOME/Library/Application Support/Shigoto"
mkdir -p "$dir"
cp ./config.json "$dir/config.json"

Order does not matter

You can copy the file before or after installing. If the sensor is already running when the file appears, it notices the change within seconds and applies it — no restart needed. The file also survives later updates, so you only have to deploy it once.

3b — Install silently

Windows

ShigotoSetup.exe /S --force-run

• /S runs the installer silently — no window, no clicks.
• --force-run starts the sensor once the installation is finished. In silent mode the installer never shows its final page, so without this flag the sensor would be installed but not started until the next login.
• --hidden (optional) skips the Start Menu entry, for rollouts where the sensor should leave no visible trace on the machine. Pass it on the first install only — later auto-updates never recreate a shortcut that is not there, so the entry stays gone. The uninstall entry under Apps & Features is unaffected, and so is a Start Menu entry that a previous, non-hidden installation already created.

Hidden installer ≠ hidden sensor

--hidden only concerns the Start Menu. Whether the sensor itself shows a window and a tray icon is a separate setting, windowFullyHidden — see Advanced. A rollout that should be invisible needs both.

For Microsoft Intune, and for hardened fleets where the installer can crash with 0xC0000374, see the Intune section in Installation, Rollout & Uninstallation — it contains a ready-made wrapper script.

macOS

sudo installer -pkg shigotoSetup.pkg -target /

The package installs the app to /Applications and starts it afterwards. A .pkg cannot take flags of its own, so the macOS equivalent of --hidden is derived from the config.json you deployed in step 3a: if it sets windowFullyHidden to everyone or anonymous, the installer also hides the app bundle from Finder. Deploy the file before the package for that to take effect. The bundle becomes visible again after an auto-update, which replaces it. Alternatively, deploy the .app bundle (os=macos-app) by copying it to /Applications with your MDM.

What happens on the user's machine

1. The sensor starts.
2. It reads config.json, finds a valid account signature, and is activated immediately — no login screen, no activation click.
3. It registers itself to start automatically — and hidden — at every login.
4. It runs in the tray (Windows) / menu bar (macOS) and reports anonymously, without ever showing a window.

The window stays hidden — that is the success signal

A sensor that finds a valid account signature is already set up, so it starts hidden and simply runs in the tray / menu bar. Your users see nothing at all, which is exactly what a mass rollout should look like: no window, no prompt, no click.

If the window does open on a machine, read it as a warning sign rather than normal behaviour — the config.json did not arrive, sits in the wrong folder, or carries no valid account signature. See the troubleshooting table below, and Window Visibility & Notifications for all the cases in which the window opens.

Checking that it worked

• On the machine: the tray / menu-bar icon is present, and %APPDATA%\Shigoto\config.json (macOS: ~/Library/Application Support/Shigoto/config.json) now contains additional fields written by the sensor, such as clientID.
• In the Admin Panel: the machines show up under your account as active sensors.
• If nothing happens: see the troubleshooting table below.

Symptom	Likely cause	Fix
Sensor asks for a login / partner	config.json is missing, in the wrong folder, or the folder is named after the partner instead of Shigoto	Check the exact path in step 3a
The sensor window opens at every start	The sensor found no valid account signature, so it considers itself not set up	Check the path in step 3a; if the file is in place, regenerate it (step 2) and make sure you saved the response body, not an error message
Sensor is installed but never started	Installed with /S only	Use /S --force-run, or wait for the next user login
Sensor reports as one single named person	The user field was filled in the config generator	Regenerate the file with an empty user field
Sensor reports to the wrong server	config.json was downloaded from the wrong host	Regenerate it from the correct BASE_URL
A UAC prompt appears on every update	Installed machine-wide	Reinstall per user

Adding personal identity later

An anonymous rollout is not a dead end. A user can sign in from the sensor window at any time and switch to a personal identity, provided your account and partner settings allow it. Which options are available is controlled by anonymousMode — see Advanced.

Related

• Installation, Rollout & Uninstallation
• Files & Folders Reference
• Advanced — all config.json options
• Security & Data Privacy