All Documentation

Documentation Everywhere else

Audit events: the Cloud Computer

The audit catalogue's Cloud Computer events: enrolling, seats' sign-ins sent to it, discussions moved to and from it.

The Cloud Computer's own page of the audit catalogue. A Cloud Computer is optional: a computer of yours in the cloud, made only when you create it, which runs a discussion only when you send one there. What it does is recorded the way your own computer's work is, with these events besides.

The Cloud Computer

TypeReported byWhenDetail carries
chat.movedMac and serverA discussion moved between the person's computers (to or from the Cloud Computer): its work was pushed to a branch and the new computer starts from it.from, to, branch
cloud_computer.seat_sentMac and serverA seat's key or sign-in was sealed on the person's computer and sent to their Cloud Computer; names only, never values.summary, hostId
cloud_computer.seat_receivedMac and serverThe Cloud Computer opened a seat's key or sign-in sent to it and can use it now.summary, refused
cloud_computer.seat_refusedMacThe Cloud Computer could not open or would not take a seat's sign-in sent to it.summary, error
cloud_env.setServerA Cloud Computer secret or variable was set at the team, repository or personal level; its name, never its value.name, level, repo
cloud_env.removedServerA Cloud Computer secret or variable was removed.name, level, repo
cloud_env.environment_savedServerA repository's Cloud Computer environment was saved: its network level, extra domains and setup script; the script by length and digest, never its text.repo, networkMode, domains, packageManagers, setupScript (lines, sha256)
cloud_env.environment_removedServerA repository's Cloud Computer environment was removed, with its network secrets and personal variables.repo, secrets, variables
cloud_env.secret_addedServerA network secret was saved for the Cloud Computer: the hosts it is for and how it is sent, never its value.id, repo, hosts, kind, header
cloud_env.secret_removedServerA network secret for the Cloud Computer was removed.id, repo, hosts
cloud_env.usedMacA run on the Cloud Computer gave its commands the account's secrets and variables for its repository; once per run, names only.names
cloud_env.refusedMacThe Cloud Computer could not open the secrets and variables sealed to it, and kept the last ones it had.error
cloud_computer.base_script_setServerA team's owner or admin set or cleared the base install script its members' Cloud Computers run.lines, sha256
cloud_computer.base_rerunServerA person asked their Cloud Computer to run the team's base install script again, after a disk snapshot was taken.boxId, snapshotId
cloud_computer.rolled_backServerA person put their Cloud Computer's disk back to the snapshot taken before the last base install re-run.boxId, snapshotId
cloud_computer.base_install_ranMacThe Cloud Computer ran the team's base install script, the first time or on a re-run.why, exitCode, ms, version
cloud_computer.terminal_openedServerThe person opened a terminal on their Cloud Computer from one of their own apps; never what was typed or shown.boxId, id
cloud_computer.preview_openedServerThe person asked for a one-time link to a dev server on their Cloud Computer.boxId, port
cloud_host.enrolledMacA Cloud Computer signed in to its account with the one-time code its broker started it with.boxId

What these do not carry

A seat's key or sign-in sent to the Cloud Computer is named, never its value: it is sealed on your computer to that Cloud Computer's own key, and the server only ever carries what it cannot open. A move names the computers and the branch the work was pushed to, never the files. A terminal event records that one was opened, never what was typed or shown.

Mac: the app reported it — on the Cloud Computer, the app running there. Server: our servers saw it.

See Also

Not what you were looking for? The help centre answers one question at a time, and the support page says how to reach a person.