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

# Console overview

> Use the Polymorfa Console to manage teams, projects, credentials, sessions, security, and billing.

The [Polymorfa Console](https://polymorfa.com/console) is the browser interface
for your account, teams, and projects. A team is the Console name for an
organization. The active team and project in the URL determine which resources
you are viewing.

## Team and project context

The team switcher shows workspaces available to your account. Project selectors
label development projects as **Sandbox** and production projects as **Live**.
Changing team or project changes the current resource scope; it does not grant
access outside your live membership.

Onboarding is available in English and Brazilian Portuguese. Select a language
from the onboarding language control.

## Customer workflows

Use the Console to:

* manage team members and projects;
* create organization keys and project tokens;
* create, pair, inspect, and control sessions;
* configure client-token rules, webhook endpoints, and embedded signup;
* review usage, credits, invoices, and billing settings; and
* manage verified email addresses, passkeys, email OTP, TOTP, social sign-in
  connections, and active browser or device sessions.

Available actions depend on the team plan, number tier, project stage, and
features enabled for your organization. The Console shows only actions available
to the active organization and project.

## API boundary

The public Platform API is available under `/v1/*`. It accepts an
organization key or verified dashboard bearer and rejects project tokens.
Server integrations that call Messaging API, MCP, or bridge operations
must use a credential supported by that operation's generated reference.

Dashboard bearers are not customer API keys and should never be copied into an
integration. Browser and mobile integrations should receive a short-lived
client token limited to the actions they need.

## Where to go next

<Columns cols={2}>
  <Card title="Teams and projects" icon="sitemap" href="/console/teams-and-projects">
    Understand membership, roles, and project stages.
  </Card>

  <Card title="API keys" icon="key" href="/console/api-keys">
    Select and scope server credentials.
  </Card>

  <Card title="Sessions" icon="link" href="/console/sessions">
    Pair and control real or testing sessions.
  </Card>

  <Card title="Billing" icon="credit-card" href="/console/billing">
    Review current plans, tiers, and rates.
  </Card>
</Columns>