# Dashboard

The Volcano dashboard: create and inspect projects, read logs and usage, manage keys, and change configuration in a browser.

The dashboard at [volcano.dev](https://volcano.dev) is the browser interface to
your projects. Sign in with your Volcano account and every project you own is
there.

It is a client of the same API the CLI uses, so nothing it creates is special.
A project, function, or database made by clicking is the same resource
`volcano` deploys to and the REST API returns.

## What you can do here

**Projects.** Create a project, see what it contains, rename it, or delete it.
The project overview is the fastest way to answer "what is deployed right now".

**Functions and frontends.** Browse what is deployed, check deployment status
and history, and open a live URL. Deploys themselves are usually better from
the [CLI](https://docs.volcano.dev/cli.md) or [Git](https://docs.volcano.dev/platform/projects/git-deploy.md), because those are
repeatable.

**Approvals.** See every approval your durable functions have asked for, or
one workflow's, filtered by time range and status. Cards count the requested,
pending, approved, denied, expired, and cancelled ones, with the approval rate
and the median time to a decision; a pie chart shows which workflows ask most,
and a second chart shows outcomes per day. Open a pending approval to read its details, then
approve or deny it with an optional comment, and the workflow resumes with your
decision. See [Durable approvals](https://docs.volcano.dev/platform/functions/durable-approvals.md).

**Durable messages.** Open a durable execution to see the messages it was sent
and published, oldest first, and the message names it is waiting on. Send it a
message from the same panel, which resumes a matching wait. See
[Durable messages](https://docs.volcano.dev/platform/functions/durable-messages.md).

**Durable Tracing.** Under **Observability → Durable Tracing**, pick a durable
function and one of its recent executions to see its trace: every step, wait,
and retry on a timeline, and how long the code ran versus waited. A failed or
timed-out execution shows its error type and message under its name when one
was recorded, ready to copy. Select an operation to see its own error and each
attempt's, when the trace has them; otherwise rely on the execution's error.
The address links to the execution shown. See
[Inspect an execution's operations](https://docs.volcano.dev/platform/functions/durable-functions.md#inspect-an-executions-operations).

**Databases.** Create a database, browse branches and backups, and read
connection details. See [Databases](https://docs.volcano.dev/platform/databases/overview.md).

**Storage.** Create buckets, browse objects, and edit access policies. See
[Storage](https://docs.volcano.dev/platform/storage/overview.md).

**Authentication.** Turn sign-in methods on, configure OAuth providers, edit
email templates, and look at the users who have signed up. See
[Authentication](https://docs.volcano.dev/platform/authentication/overview.md).

**Logs and usage.** Search logs across functions, frontends, and databases, and
see what the project is consuming against your plan. See
[Logs](https://docs.volcano.dev/platform/functions/logs.md) and
[Plans and limits](https://docs.volcano.dev/platform/guides/plans-and-limits.md).

**Variables and keys.** Set environment variables, and create or revoke anon
keys, service keys, and project access tokens. See
[Token types](https://docs.volcano.dev/platform/authentication/security/token-types.md).

**Domains.** Attach custom domains to a frontend, and make one redirect to
another. See [Custom domains](https://docs.volcano.dev/platform/frontends/overview.md#custom-domains).

## When to use something else

The dashboard is the right tool for looking at things and for changes you are
not going to make twice. Two jobs belong elsewhere:

- **Anything repeatable.** A deploy you will run again, a migration, or a step
  in CI belongs in the [CLI](https://docs.volcano.dev/cli.md), where it can be scripted and reviewed.
- **Anything your application does at runtime.** Signing users in, querying
  with row-level security, uploading files — that is an [SDK](https://docs.volcano.dev/sdk/js.md), not a
  person in a browser.

## Reading a project's configuration as a file

Much of what the dashboard edits also lives in
[`volcano-config.yaml`](https://docs.volcano.dev/platform/projects/configuration.md), the declarative manifest
for a project. `volcano cloud config pull` writes the project's current
configuration to that file, and `volcano cloud config deploy` applies it. Use it
when you want configuration reviewed in a pull request rather than changed by
clicking.