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

# User guide

> Navigate MoleSignal, choose a workspace, keep time context, and move from a signal to an investigation.

This guide explains the product shell and common behavior across signal-specific pages.

## Sign in and choose a workspace

Sign in with email and password or an enabled SSO provider. MoleSignal opens the home route saved
in personal preferences.

Use the workspace switcher in the top bar for memberships in multiple organizations. Switching a
workspace refreshes the signed context and capability snapshot. Pages available in the previous
workspace can disappear when the new role lacks equivalent permissions.

<Note>
  The UI uses **workspace** for the current organization. API fields and IAM permissions use
  `organization` and `org_id`.
</Note>

## Product areas

| Area                      | Purpose                                                                                   |
| ------------------------- | ----------------------------------------------------------------------------------------- |
| **Home**                  | Review signal health, active incidents, intake status, and quick starts.                  |
| **Logs**                  | Search events, inspect fields, and open surrounding context.                              |
| **Metrics**               | Run PromQL, inspect series, and analyze cardinality or data quality.                      |
| **Traces**                | Browse traces, inspect spans, and open the service graph or catalog.                      |
| **APM**                   | Analyze service RED metrics, transactions, dependencies, backend errors, and deployments. |
| **Continuous Profiling**  | Analyze CPU, memory, and contention flame graphs.                                         |
| **RUM**                   | Review browser sessions, frontend errors, Web Vitals, and source maps.                    |
| **Dashboards**            | Build reusable panels and variable-driven views.                                          |
| **Alerts**                | Manage incidents, rules, channels, schedules, and response policies.                      |
| **Mole Agent**            | Ask Mole Agent to investigate and review controlled operations.                           |
| **Streams and Pipelines** | Manage data contracts, transforms, routing, and backfills.                                |
| **IAM and Settings**      | Manage people, permissions, workspace policy, security, and platform settings.            |

Navigation is capability-driven. MoleSignal hides routes that the current workspace scope cannot
use instead of showing controls that will always fail.

## Keep time context

The global time picker controls the active query window. Query pages may temporarily override the
default timezone, date format, and time range.

Cross-signal drills carry the time anchor and correlation fields. For example, a trace-to-log jump
keeps the trace window and adds the `trace_id` filter.

## Search and investigate

Press `⌘K` or `Ctrl+K` to open the command palette. Search for product routes, streams, dashboards,
saved views, alerts, incidents, and services.

A typical investigation follows this sequence:

<Steps>
  <Step title="Start from the symptom">
    Open an incident, a dashboard panel, a slow trace, a frontend error, or a hot profile.
  </Step>

  <Step title="Narrow the time and resource">
    Select the smallest useful time window and pin the service, stream, environment, or session.
  </Step>

  <Step title="Pivot across signals">
    Use the correlation actions to open related traces, logs, metrics, profiles, or RUM sessions.
  </Step>

  <Step title="Save or automate">
    Save a query, add a dashboard panel, create an alert, or turn a repeatable workflow into a
    Mole Agent investigation or automation.
  </Step>
</Steps>

## Account preferences

Open the user menu and choose **Account settings** to manage:

* profile, avatar, and bio;
* theme, density, language, timezone, and date/time format;
* default home route and keyboard shortcuts;
* password-reset entry points and the current browser session;
* workspace membership and stable identifiers.

Personal preferences override workspace defaults. A query page can still apply a temporary
time-display override for the current investigation.

## Next steps

<CardGroup cols={2}>
  <Card title="Explore logs" icon="file-lines" href="/en-US/logs">
    Search, filter, inspect context, and save a view.
  </Card>

  <Card title="Explore metrics" icon="chart-line" href="/en-US/metrics">
    Build PromQL and analyze series behavior.
  </Card>

  <Card title="Explore traces" icon="route" href="/en-US/traces">
    Inspect span trees and service relationships.
  </Card>

  <Card title="Analyze services with APM" icon="gauge-high" href="/en-US/apm">
    Find slow transactions, failing dependencies, errors, and deployment regressions.
  </Card>

  <Card title="Administration" icon="shield" href="/en-US/administration">
    Understand organization and platform administration.
  </Card>
</CardGroup>