Sidekick for Teams — For IT
Rollout, keys and security
What runs where, how to deploy it, and how keys reach people.
01
What goes where
Sidekick runs on the computer. Your documents stay there; error reports can hold fragments of the code the assistant ran (see Document content).
-
api.polar.shWhenAbout once a day while InDesign is open, even without Sidekick useTurn offNo: it is the license check. Blocked or offline: a key accepted before keeps working, with no time limit. -
localhost:6001WhenWhile Sidekick runsTurn offNever leaves the computer -
releases.sidekick.eastpole.nlWhenSidekick starts, plugin connectsTurn offPin the version -
us.i.posthog.comWhenUsage and error reportsTurn offTelemetry off
What Polar receives
- The license key and the computer's IP address.
- When the seat is activated, a label: Adobe account email and OS, e.g.
[email protected], macOS. - A hash of the Adobe account ID.
Polar is the seller and processes seat holders' email addresses in the United States. Each seat holder sees their own key in Polar's portal, with its labels and how often and when it was last checked. The buyer sees who holds each seat, not the keys. East Pole sees every key's labels and when it was last checked: so when someone last started InDesign.
Document content
When code fails in InDesign, the error report holds its first 500 characters. The assistant writes that code: mostly layout instructions, sometimes fragments of text being written into the document. Telemetry off stops these reports.
What the assistant reads goes to its maker, under your agreement with them. See the privacy policy.
Telemetry
On by default, anonymous.
| One person | Ask the assistant: "disable Sidekick telemetry" |
| The organization | "telemetry": false in managed-settings.json. People can't turn it back on. |
02
Rollout
Two things reach each computer: the plugin, and the person's key.
1 — The plugin
2 — The key
Uninstall Sidekick for InDesign (from Adobe Exchange) first: only one Sidekick plugin connects at a time.
Admin Console package
- Turn on create a folder for extensions.
- Include the Unified Plugin Installer Agent (UPIA).
- Put
sidekick-direct-1.0.38.ccxin that folder.
InDesign must be in the package or already installed. A failed plugin does not stop the package: check with Plug-Ins > Sidekick Direct > Sidekick, or UPIA's list.
UPIA from the command line
macOS
"/Library/Application Support/Adobe/Adobe Desktop Common/RemoteComponents/UPI/UnifiedPluginInstallerAgent/UnifiedPluginInstallerAgent.app/Contents/MacOS/UnifiedPluginInstallerAgent" --install /path/to/sidekick-direct-1.0.38.ccx Windows
"C:\Program Files\Common Files\Adobe\Adobe Desktop Common\RemoteComponents\UPI\UnifiedPluginInstallerAgent\UnifiedPluginInstallerAgent.exe" /install C:\path\to\sidekick-direct-1.0.38.ccx List what is installed: --list all (macOS), /list all (Windows).
Verify the file
Not signed by Adobe: it does not come through Adobe's Marketplace. A published file never changes: each version has its own address, with its SHA-256 checksum beside it.
Version 1.0.38: sidekick-direct-1.0.38.ccx, checksum in sidekick-direct-1.0.38.ccx.sha256:
f43c255eeb66381eea31b288c908879c871b9d4224b888b588e9ff6d8869371a
shasum -a 256 sidekick-direct-1.0.38.ccx # macOS
Get-FileHash sidekick-direct-1.0.38.ccx -Algorithm SHA256 # Windows 03
Keys
One key per person, one activation each, tied to that person's Adobe account. No organization-wide key.
The license file, for MDM
Write it as the signed-in user; create the folder if needed. Every InDesign version shares it.
| macOS | ~/Library/Application Support/indesign-sidekick/license.json |
| Windows | %USERPROFILE%\.indesign-sidekick\license.json |
{ "version": 1, "key": "SIDEKICK-..." } // UTF-8 JSON The plugin keeps its own data in this file too: in an existing file, change only key.
The first computer a person uses activates the seat, and the plugin adds an activation
to the file. For a second computer of the same person, copy the whole file from the first. It works only
under the same Adobe account. A file with only the key gets "Seat already in use" there.
Many people: Polar's API
The portal takes one email at a time. With the buyer's portal session (the token in the portal's URL, sent as Authorization: Bearer; short-lived, so sign in for each run):
# assign, claimed at once, no invitation email
POST https://api.polar.sh/v1/customer-portal/seats
{ "subscription_id": "...", "email": "[email protected]", "immediate_claim": true }
# your subscription's id
GET https://api.polar.sh/v1/customer-portal/subscriptions/
# list seats: status and email per seat, and how many are free
GET https://api.polar.sh/v1/customer-portal/seats?subscription_id=...
# revoke
DELETE https://api.polar.sh/v1/customer-portal/seats/{id} Keys are not in this listing. A key is shown only to its seat holder, signed in to the portal with their own email address. For the license file, each person passes you their key, or enters it in the panel themselves.
Rotating keys, removing activations
Rotate: the seat holder does this, in the portal. The old key stops at once. Push the new key right away; activated computers stay activated. Revoking a seat and assigning it to the same person again gives back the same key.
Remove an activation in the portal and Sidekick stops on the computers that use it. The panel says "Computer removed from seat"; the person clicks "Activate this computer again". Only the seat holder can remove one.
"Seat already in use": the seat is active for another Adobe account or on another computer. The seat holder removes that activation in the portal, or copy the license file if the other computer is the same person's.
04
Known limits
- The assistant can read the key In the license file, through Sidekick's
executetool. - No shared computers Classrooms, labs, virtual desktops without a lasting profile, Adobe Shared Device Licensing: not supported. A seat is one person, tied to their Adobe account.
- No updates through Creative Cloud Sidekick itself still updates. Reinstall the plugin only when we tell the buyer: when the license check or the protocol changes.
Questions from a security review? [email protected]