DK Studio/Documentation
ProductChangelog

Personal Center

The Personal Center is where you manage the machines that belong to you. It holds two things: the personal licences you issued, and the machines those licences registered.

Everything here is yours alone. You issue your own personal licences from this page; the shared lab has its own licences, issued by an administrator under Admin → Licences. That page lists the personal licences people have issued as well — an administrator can see who holds what and revoke one — but the Personal Center is where you manage yours.

Why there is a licence at all

A machine does not apply for anything. It cannot decide to join a lab, and there is no "self service onboarding" where a machine announces itself and whoever confirms it becomes the owner. Instead, a person signs in to the studio and issues a licence for themselves. The licence says what the machine that claims it will be.

Licence typeWho issues itWhat the machine becomes
personalYou, from this pageA machine that belongs to you
labAn administrator, from Admin → LicencesA bench that belongs to the shared lab

The licence type decides the ownership, not where the machine physically sits. A personal licence used on a bench in the lab still gives you a personal machine.

Issuing a personal licence

Press Apply for a license at the top of the page. The studio creates a licence and shows its code once:

dk_l_9f4c1e7a2b8d4063a5c9e13f7d2b6084

Copy the code — it is the only way into the studio, and it is not shown again. Then enter it on the machine under test, on the agent's own page at http://localhost:3001. The agent registers with it, the licence is spent, and the machine shows up in the list below.

One licence, one machine. A licence authorises exactly one registration, and it is spent on that registration, so the same code cannot bring up a second machine. Issue one licence per machine.

Copy the code before you close the dialog

The code is shown once, at issue. If you lose it, revoke the licence and issue a new one.

Your licences

The list shows every personal licence you have issued, with its status.

StatusMeaning
pendingIssued, not yet claimed by a machine.
consumedClaimed by a registered machine.
revokedRevoked by you. The code no longer registers anything.
expiredPast its expiry date.

A pending licence can be revoked from this page. A consumed licence cannot — the machine it registered is still on the books, and it points at that licence. To retire that machine, delete the agent itself. An administrator can revoke any pending licence from Admin → Licences, personal ones included.

Your machines

The machines list shows the agents that registered with one of your personal licences. Each row carries the machine's name, its location or label, the date it registered and its status.

A machine registered with a personal licence appears under My Computer in the studio, and only you see it. It never appears under the Lab scope, even when it sits on a bench in the lab.

Doing it over HTTP

The same three things are available as endpoints.

# Issue a personal licence
curl -X POST http://studio.lab.internal:3000/api/licenses \
  -H 'Content-Type: application/json' \
  -H "Cookie: session=$SESSION" \
  -d '{"type":"personal"}'
 
# List your licences and machines
curl http://studio.lab.internal:3000/api/licenses \
  -H "Cookie: session=$SESSION"
 
# Revoke a licence you have not spent
curl -X POST http://studio.lab.internal:3000/api/licenses/<id>/revoke \
  -H "Cookie: session=$SESSION"
GET/api/licensesList the licences you own and the machines you can see.
POST/api/licensesIssue a licence. `type` is `personal` or `lab`.
POST/api/licenses/{id}/revokeRevoke a licence you own. A consumed licence cannot be revoked.

Next steps