---
title: "The web app"
description: "A tour of the Overlane web app, view by view, and how it relates to the CLI, the API and the connections you choose to add."
---

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

# The web app

The web app is the same service the CLI and your agents use, shown as a workspace. It reads and writes through the public API only, so anything you can do in a view you can also do from the CLI or the API, and what a role may do is decided by the service, not by the page. See [Roles in the web app](/web-app/roles/).

Overlane provides each of these areas itself. Projects, pull requests and review, issues, CI, deploys, memory and observability work with no third-party account. GitHub, Linear and other services are connections you can add; a record that lives on one shows its provider beside it, and a record with no provider is native to Overlane.

## Views

The sidebar follows the life of a change: **Home** (Overview, Inbox), **Work** (Projects, Issues, Runs, Reviews), **Delivery** (CI, Releases, Deploys, Observability), **Knowledge** (Memory) and **Workspace** (Settings). On a phone the bottom bar holds Overview, Issues, Runs and Reviews, and the rest is under More.

| View | What it shows | Who can change things |
| --- | --- | --- |
| Overview | The front page of the workspace, in the order a change travels: **Needs you**, **Projects** and **The work**. It reuses data the app has already loaded. | Read only. |
| Inbox | What needs you: failed pipelines and deploys, approvals, alerts and runs that stopped on an error. Choose what reaches you in [notifications](/web-app/notifications/). | Anyone who can see the item. |
| Projects | Every project in the workspace and where its code lives. A project can be hosted on Overlane or connected from a provider. A project page is a hub of links plus one **Project settings** button. | Members and above create projects. Changing a project's code-map setting needs policy rights. |
| Issues | Work to do, with a filter box, grouping and saved views. See [Saved views](/web-app/saved-views/). | Members and above create and edit issues. |
| Runs | What an agent is doing right now. A new event appears within seconds, and a dropped connection resumes from the last event it saw, with none missed or repeated. Cost and logs sit beside the events. | Read only. |
| Reviews | Each pull request with its findings. Deterministic checks (linters, the type checker, the secret scanner, policy rules) are listed first; the optional model pass comes after and is labelled as untrusted text. | Members and above dismiss a finding. A blocker from a deterministic check cannot be dismissed; fix it instead. |
| Memory | What your team and agents have decided and learned, with scope, who observed it and its status. Memory text is shown as data and is never an instruction. | Members and above add and confirm memory. |
| CI | Pipeline runs and their steps. | Members and above re-run a pipeline. |
| Releases | Signed releases, their channels and which projects run them. See [release channels](/releases/). | Depends on the action. See [roles](/web-app/roles/). |
| Deploys | Environments, releases, checks and approvals. | Owners and admins approve and roll back. An approval is offered only while the deterministic checks have passed. |
| Observability | Cost by agent and project, and logs. | Read only. |
| Settings | The index groups its pages by audience: **Workspace** (workspace, members, notifications, account, memory), **Project** (General, Code, Repository, CI, secrets, environments, releases, routing, reviews, observability), **Agents** (agent access, bots, API keys, [usage policy](/web-app/usage-policy/)), **Policy and security** (guardrails, budgets, decisions, file claims, the [audit log](/web-app/audit-log/), enterprise), **Integrations** (connectors, chat approvals, webhooks, issue sync, library docs) and **Billing** (plan, usage and deploys). Project pages act on the project chosen in the picker above the page. See also [members and roles](/web-app/roles/). | Depends on the page. |

Every view has four states: loading, empty (with the way to add something), error (with a retry) and offline (it shows the last data it has and refreshes when the connection returns). Each one works at 360 px wide, in both themes, with a visible focus ring and reduced-motion support.

## Sample data

The Reviews, CI, Deploys, Runs and Observability views switch to live data as those services are connected to your workspace. Until then a view says so in a "Sample data" note at the top, and nothing you do in it is saved.

## Signing in

You sign in with email, a passkey, a linked provider such as GitHub or Google, or your company's single sign-on. The web app keeps a secure, HTTP-only session cookie that the service checks on every request; sign out from the account menu to end it. Agents never use this cookie: they [sign in from the CLI](/agent-tokens/).

## Keyboard

Everything above can be reached from the keyboard. See [Keyboard shortcuts and the command palette](/web-app/keyboard-shortcuts/).

Source: https://docs.overlane.app/web-app/index.mdx