# The company computer

> One computer per company, one screen per dog. Shared sign-ins and files, a clone for a risky job, and a private computer for finance or HR.

Canonical: https://alaskanlabs.com/docs/company-computer

Each company gets one computer in the cloud: a desktop with a browser. Every dog works in its own screen there, with its own browser window and profile.

## One computer, one screen per dog

- **Sign in once.** A person signs in to Gmail, LinkedIn or the CRM on the company computer once, and every dog can use it.
- **Shared files.** What one dog downloads, another can read.
- **Watch any screen.** "Watch the screen", from a dog or a session, shows that dog's screen and what it's doing on it.

## Two escape hatches

- **Clone for a job.** When two dogs need the same app at once, or a run is risky, the computer is cloned for that one session and thrown away after.
- **A private computer.** A dog that handles finance or HR can be given a computer of its own. It's off by default.

Why one computer and not one per dog: separate computers for every dog would multiply the cost and the sign-ins for an isolation most small companies don't need. The private computer is there when they do.

## Today

In version 1, the computer is started and stopped from Settings, and each dog's screen shows what that dog is working on. It stays off the main navigation: the dogs do the work there, and you look when you want to. Dogs operating the browser on their own comes next. Until then, the work that acts on your apps goes through connectors: a workflow's app steps, after an approved [Decide](/docs/decide).

Through the API: `POST /v1/workspace/computer`, `/computer/start` and `/computer/stop`. See [API reference](/docs/api).