# Console overview

> The console at console.extension.dev is where a repository becomes an extension with builds, releases, and store submissions. This page maps every route.

Canonical: https://docs.extension.dev/console/overview
This page as Markdown: https://docs.extension.dev/console/overview.md
Section: Console: build and release
Siblings: [Usage and limits](https://docs.extension.dev/console/usage.md) · [Builds](https://docs.extension.dev/builds/overview.md) · [Channels](https://docs.extension.dev/builds/channels.md) · [Releases](https://docs.extension.dev/builds/releases.md) · [Store releases](https://docs.extension.dev/builds/store-releases.md) · [Release gates](https://docs.extension.dev/builds/release-gates.md) · [Integrity](https://docs.extension.dev/builds/integrity.md)
Map of every page: https://docs.extension.dev/llms.txt · Whole corpus: https://docs.extension.dev/llms-full.txt

---

# Console overview

The console at [console.extension.dev](https://console.extension.dev) is
where a repository becomes an extension with builds, releases and store
submissions. Reach for this page when you are signed in and want to know
where everything is.

## Quick start

```text
https://console.extension.dev/<workspace>/<repo>
```

The project opens on its **Overview** tab, and the other four tabs hang off
that address as `/activity`, `/builds`, `/releases` and `/submissions`.


## How it works

### Two layers

The console has two layers. Global routes belong to you. Everything else
belongs to a workspace, which answers at `/<workspace>`.

Three global addresses hand off to another surface. `/import`, `/templates`
and `/new/templates` land you on the surface that owns them, which is why
the address bar changes.

### Workspace settings

Workspace settings live at `/<workspace>/settings` in seven sections, each at
its own address: **Workspace**, **Members**, **GitHub connections**, **Store
accounts**, **Plan and limits**, **Usage** and **Danger zone**. **Store
accounts** holds the store keys every project in the workspace submits with,
and only an owner connects or disconnects one. **Plan and limits** prints
what the plan allows beside what the workspace has spent. **Usage** counts
the builds per project. See [Usage and limits](/console/usage).

### A project

A project lives at `/<workspace>/<repo>` under a five-tab strip. **Overview**
is the project root, and the other four hang off it. A sixth address,
`/checks`, answers without a tab: the console has no verdict to show there
yet.

Project settings are a dialog with its own address,
`/<workspace>/<repo>/settings/<section>`. Every section is linkable, so you
can send a teammate straight to the one that matters. `/settings` on its own
redirects to `general`, `/project-settings/<section>` forwards to the same
section keeping its query and hash, and closing the dialog returns you to
the project overview.

**Visibility** decides who can open this project's builds. It offers public
and private, and only workspace owners and admins can change it. The section
lists what the change means before you confirm it, and it warns you when the
setting saved but the public pages have not caught up. Visibility also
decides whether a share link carries a token. See
[Publish a build](/tools/publish) and
[Public project pages](/share/public-pages).

### The lifecycle

Every project moves through the same four verbs.

**Connect.** `/import` or `/new` links a repository, and the template gallery
behind `/new/templates` creates one from a template. The console reads the
manifest and configures a build per declared browser.

**Build.** Push a commit. The project builds one artifact per browser and
records it under **Builds**. Open `/builds/<buildId>/<browser>` for the
artifact, its logs and its integrity record.

**Release.** A build becomes a release at `/releases/new`, in a channel.
Every project starts with two, `preview` and `stable`. The form shows the
build's version as a fact and never changes it. `preview` takes any build;
`stable` and every channel you create take a build made for Stable. When the
build was not, the form offers **Rebuild for Stable · 1 build.** Until
something lands on `stable`, the Releases tab reads **Nothing on Stable yet. Release a
build here, or submit one to a store.**
**Create release** dispatches one release run per browser and hands you to
the release page at `/releases/<releaseId>`, where the release id is the
channel name. Its **Rollout** section reports each browser's release run and
refreshes on its own while a run is in flight. The page also holds the
channel's current build and the timeline of what entered it. The **Roll
back** control sits in its header. Owners see it once the channel has an
earlier build to return to. Members see it disabled, with a note that only
owners roll back. To ship a version no build carries yet, **Bump version**
at `/releases/bump` opens a pull request that raises the manifest version
and reads **Pull request opened** from GitHub's answer.
See [Releases](/builds/releases).

**Submit.** A build that passed goes to the stores from the **Submissions** tab.
A submission takes a build made for Stable, and `stable` moves for that
browser once the store records the submission. Each submission is tracked
at `/submissions/<store>/<submissionId>` until the store answers. A store
account is connected once, by the project under **Stores** or by the
workspace under **Store accounts**, and is never held by your machine.

## Reference

### Global routes

| Route | What it does |
| --- | --- |
| `/` | Sends you to your workspace. Signed out, it sends you to the home page, which brings you back once you sign in |
| `/new` | Pick a repository to connect, with doors to the template gallery and the code app above the picker |
| `/new/templates` | Browse the template catalog. Answered by `templates.extension.dev` |
| `/new/code` | Open the code app when that lane is on. Otherwise it returns you to `/new` |
| `/import` | Connect a repository you already have. Answered by `www.extension.dev/import` |
| `/templates` | The same door as `/new/templates` |
| `/hello` | Create a workspace: name, description and developer URL |
| `/shares` | Sends you to your workspace home. Share links live in project settings under **share-links** |
| `/founders-note` | Hands you to the one copy of the note on `www.extension.dev` |

### Workspace settings

| Section | Address |
| --- | --- |
| **Workspace** | `/<workspace>/settings/workspace`, also the bare `/settings` |
| **Members** | `/<workspace>/settings/members` |
| **GitHub connections** | `/<workspace>/settings/connections` |
| **Store accounts** | `/<workspace>/settings/store-accounts` |
| **Plan and limits** | `/<workspace>/settings/plan` |
| **Usage** | `/<workspace>/settings/usage` |
| **Danger zone** | `/<workspace>/settings/danger` |

### Project tabs

| Tab | Address | Contents |
| --- | --- | --- |
| **Overview** | `/<workspace>/<repo>` | The manifest, configured browsers and current state |
| **Activity** | `/activity` | What happened, in order |
| **Builds** | `/builds` | One row per build, one artifact per browser |
| **Releases** | `/releases` | Builds released to a channel |
| **Submissions** | `/submissions` | Store connections and submissions |

### Project addresses

| Address | Opens |
| --- | --- |
| `/builds/<buildId>` | One build |
| `/builds/<buildId>/<browser>` | One browser's artifact, logs and integrity record |
| `/releases/new` | The new release form. It releases a build that exists. A `?version=` link with no `build` sends you to `/releases/bump` |
| `/releases/bump` | The **Bump version** page. It opens a pull request that raises the manifest version |
| `/releases/<releaseId>` | One channel's release page, with its **Rollout** section |
| `/submissions/<store>` | One store |
| `/submissions/<store>/history` | Every submission to that store |
| `/submissions/<store>/new` | A new submission |
| `/submissions/<store>/<submissionId>` | One submission |
| `/submissions/new` | Sends you to project settings, **Stores** |
| `/connect/<store>` | The connect page an agent hands you for one store: paste the store's key, or continue with Google for Chrome. The platform checks it with the store before it saves anything |
| `/stores...` | Old addresses. Each redirects to its `/submissions` twin |
| `/checks` | Answers without a tab |

### Project settings sections

| Section | Address |
| --- | --- |
| general, team, environment, build, deployment, github, channels, stores, visibility, public-page, access-tokens, share-links, connected-apps, danger | `/<workspace>/<repo>/settings/<section>`, also `/project-settings/<section>` |

## When it fails

- **A workspace route says it is not available to you.** You are signed in
  to an account that is not a member. Check **Members** from an account that
  is.
- **A push builds nothing.** The GitHub connection lapsed. Reconnect under
  project settings, **github**.
- **A release page shows no rollback control.** The channel has nothing
  behind its current build. See [Releases](/builds/releases).
- **A link to `/releases/new` opened Bump version.** The link carried a
  version and no build. The release form reads the version from the build,
  so a version alone asks for a bump, and the link lands on `/releases/bump`
  with that version and channel.
- **A submission sits in review.** That wait belongs to the store. The
  submission page shows the last state the store reported.
- **A submission reads Unknown.** The run ended without a state the console
  could read from the store. It is not a submission that succeeded. Open the
  run and read the failure. See [Publishing](/publish/overview).
- **A stranger cannot open a build page you expected to be public.** The
  project is not declared public, or the public pages have not caught up.
  Check **Project settings, Visibility**. See
  [Public project pages](/share/public-pages).

## Next

- [Usage and limits](/console/usage)
- [Release gates](/builds/release-gates)
- [Access tokens](/tools/access-tokens)
- [Share an unpublished build for review](/share/unpublished-build-for-review)
