---
title: "The console"
description: "The console is the browser view of an organisation's schema, its history, and the controls around applying it."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.tryatlantis.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# The console

The console is the browser view of your organisation's schema, its
history, and the controls around applying it. It shows state and is where
approvals are decided. Schema changes themselves travel through `tide`
from a repository; the console has no schema editor.

You sign in at Atlantis Cloud, and the console holds no accounts of its
own. Every page is scoped to one organisation, and an account in more than
one switches between them in the sidebar.

## What the pages divide into

Most of the console records what has already happened: the merged schema,
the version history, connected workers, live server activity, parked
objects, the audit log. These pages answer "what is true now, and how did
it get that way".

A smaller set decides or changes something: Approvals holds plans waiting
on a person, Callers governs which repositories may talk to the server and
how much each may do unattended, Settings carries the organisation's
policies, and Operations executes a rollback or retries dead work. Every
page is listed in the [console reference](/reference/console/).

## Reading and deciding

Reading is open to every signed-in user: the schema, history, plans,
rehearsal results, policies, workers, the audit log.

Deciding is gated twice. Your role in the organisation — `viewer`,
`developer`, or `admin` — decides which actions exist for you at all, and
the actions that grant authority need a fresh re-authentication at Cloud,
so a stolen session cookie alone cannot exercise them. Approving a plan
needs that second gate; rejecting one does not, because a rejection grants
nothing.

## Roles

Roles are cumulative. A `viewer` reads. A `developer` also boots
sandboxes, triggers rehearsals, and decides plans for any change class
whose policy names `developer` as the approver. An `admin` can do
everything, including the actions that change who may talk to the server.

The [console reference](/reference/console/#roles) states each role's
surface, and support sets a member's role — the Members panel is
read-only.

## Related

- [Console reference](/reference/console/) — every page, panel, and sudo-gated action.
- [Change approval](/concepts/change-approval/) — the gates the Approvals page decides.
- [Use the sandbox](/guides/use-the-sandbox/) — the Sandbox page, step by step.
- [Manage members and callers](/guides/manage-members-and-callers/) — registration, enrolment, and per-caller policy.

Source: https://docs.tryatlantis.dev/concepts/the-console/index.mdx