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

# Dashboard and settings

> Know where to launch work, inspect tasks, and manage the deployment setup.

The web app is where admins set up a Roomote deployment and where reviewers
inspect the full task record.

Chat, source control, and Linear may be where work starts, but the dashboard
is where you manage the operating surface and review the detailed evidence.

## Home

Use **Home** to launch a task directly from the web app when you want to
choose the environment yourself or start from a prompt instead of an external
thread.

Home is also where new deployments see setup and onboarding guidance, recent
task activity, and prompts to finish key connections such as source control or
chat.

## Tasks

Use **Tasks** to review active and completed work across the deployment.

The task view is the main review surface. It can show:

* the conversation and follow-up history
* terminal output and logs
* artifacts such as plans or reports
* previews for running apps
* diffs and PR links for code changes

Read [Review a task](/tasks) for the practical review flow.

## Automations

**Automations** is where admins configure background Roomote work such as PR
review, merge-conflict resolution, and recurring triage or summaries. Read
[Automations](/automations) for the full list.

## Settings

Settings is where admins shape how Roomote works for the deployment. Members
also use it for their own linked accounts and personal profile settings.

| Area                              | Who uses it | What it controls                                                    |
| --------------------------------- | ----------- | ------------------------------------------------------------------- |
| [Personal](/personal-settings)    | Everyone    | Profile details, linked accounts, theme, and app preferences        |
| Models                            | Admins      | Enabled inference providers, task models, and the default model     |
| Communications                    | Admins      | Communications providers: Slack, Microsoft Teams, and Telegram      |
| Compute                           | Admins      | Compute providers that run task sandboxes                           |
| [Integrations](/integrations)     | Admins      | Built-in integrations that give tasks extra context                 |
| [Environments](/environments)     | Admins      | Source control, repositories, services, and workspace configuration |
| Live Previews                     | Admins      | Live preview enablement for task sandboxes                          |
| [Agent Guidance](/agent-guidance) | Admins      | Shared instructions that apply across tasks                         |
| [Skills](/skills)                 | Admins      | Environment-level playbooks and custom skills                       |
| Users                             | Admins      | Who can access the deployment                                       |
| [Vibes](/vibes)                   | Admins      | Tone and summon behavior that helps Roomote fit your team           |
| Experimental                      | Admins      | Deployment-wide feature flags                                       |

## A practical order for new admins

If you are just getting started, this order usually works well:

1. connect source control and chat
2. connect an inference provider and compute provider
3. create the first environment
4. review the environment setup task
5. run a small first task
6. add the next integration or automation only after the first path feels
   stable

## When to stay in the dashboard

Prefer the dashboard when you need to:

* inspect the full task output
* compare logs, artifacts, diffs, and previews
* continue or resume an existing task
* manage environments or deployment settings
* review work that started in chat, source control, or Linear