# Using atmon

The console is one screen per thing you might want to do. This section is written the same way: pick what you are trying to do, not which part of the system you think owns it.

Sign in at [atmon.ai/console](https://atmon.ai/console/).

## The screens

| Screen | What it answers |
|---|---|
| Overview | Is anything waiting on me, is anything broken, what did today cost. |
| Inbox | Questions and approvals addressed to a person. |
| Jobs | Every piece of work that has run, is running, or is parked. |
| Standing | The work that runs on its own, on a schedule or when something happens elsewhere. |
| Connect | Every app this project can reach, and the accounts connected to each. |
| Build | Build a private tool for this project and test it before anything routes to it. |
| Storage | Point this project's files and collections at a bucket of your own. |
| Model | The model that reads and writes text inside a job, and what it costs. |
| Policies | What may be done, what may be spent, and who may change either. |
| Governance | Where the money went, how the apps are behaving, and what the exports say. |

Two more sit outside the project, because they are about the organization rather than about one project: **Members** and **Billing**.

## The pages here

| Page | Covers |
|---|---|
| [Connect an app](./connect-apps.md) | Connecting accounts, for yourself and for your users |
| [Approvals and questions](./approvals.md) | The inbox: releasing a call, answering a question |
| [Jobs](./jobs.md) | Handing over work that is bigger than one call, and reading it back |
| [Standing work](./standing-work.md) | Work that starts on a schedule or on an event |
| [Private tools](./private-tools.md) | Bringing a tool of your own, and the gate it passes first |
| [Policies](./policies.md) | Rules, spending ceilings, and who may write them |
| [Members and billing](./members-and-billing.md) | Who is in the organization, and what it pays for |

## Two ideas that run through all of it

**A project is the boundary.** Keys, rules, connected accounts, receipts, and spend all belong to one project. An organization can hold several, which is the usual way to separate staging from production.

**An entity is a person you name.** Every action is taken on behalf of one, and the string is yours to choose: whatever id your own product already uses for that user. A connected account belongs to an entity, so an action taken for one person can never reach another person's credential.