Using the Dashboard¶

The Astrolift dashboard is the browser client for the same control plane used by the CLI, API, and MCP gateway. Available modules and actions depend on the active install, your organization role, and the modules enabled for that role.

The sidebar has two complementary views:

The workspace tree groups teams, projects, apps, agents, and workflows. Expand a row to move through the hierarchy.
The module switcher opens Dashboard, Apps, Agents, Workflows, and Admin. The server decides which modules your account can see.

Apps contains links to Deployments and Approvals. Agents contains the Fleet Map. Workflows contains Jobs, Tasks, and Functions. Admin is grouped into Organization, Infrastructure, Usage & Governance, and Platform Signals.

Docs and Downloads are in the sidebar footer. The Astrolift brand chip shows the organization attached to this install; it is a label, not an organization switcher.

Entity pages¶

An app page is organized into five pillars:

Build — Config, Manifest, and Webhooks.
Run — Overview, Deployments, Environments, Jobs, Workloads, Topology, and Previews.
Observe — Observability and Logs.
Control — Shell, Commands, Domains, Managed Services, Settings, and Members.
Secure — Security, Secrets, and Tokens.

Agent pages use the same app-platform surfaces where they apply, plus agent-specific run and control views. A page may exist but remain hidden when its module is disabled or your role cannot read it.

Keyboard and accessibility¶

Ctrl-K or Command-K opens the command palette.
? opens the keyboard-shortcut reference.
/ focuses the first enabled input on the page.
g followed by the displayed destination key navigates to common pages.
Tab from page load reveals Skip to main content.

The sidebar can be collapsed and resized. Collapsed sections and sidebar width are saved in local browser storage.

Language and theme¶

The footer exposes the locale picker and light/dark/system theme controls. These preferences are local to the browser session/profile.

Permissions¶

Top-level module visibility comes from the server-authoritative module capabilities returned for the current user. Individual buttons and mutations perform finer permission checks. Hiding a button is not the security boundary: the API checks the permission and tenant scope again.

Some sensitive operations, including secret reveal and elevated administration, may require explicit elevation or approval even when the user otherwise has the relevant role.

Where to go next¶

Working with apps covers registration, deployment, configuration, secrets, and app operations.
Running an org covers organization administration and platform-wide signals.
The in-product Docs module describes the version actually running on your install.