> ## 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.

# Teams and projects

> Organize members, credentials, sessions, and integrations without crossing project boundaries.

The Console calls an organization a **team**. A team owns its members, billing,
organization keys, projects, and organization-level audit history. A project
groups sessions, project tokens, webhooks, templates, campaigns, and
integration settings.

## Roles

Team roles are:

* **Owner** — manages the team and can perform owner-restricted actions.
* **Admin** — can manage members and project resources allowed to admins.
* **Member** — can use resources allowed by the current membership and project
  policy.

Invitations can assign `admin` or `member`. Ownership is not an invitation role.
Authorization is checked against the current membership, so a role or
membership change can affect the next request.

Select a team during onboarding to make it the active organization. Onboarding
supports English and Brazilian Portuguese; selecting a language updates the
remaining steps.

## Project stages

Projects have a development or production stage. The Console labels these as
**Sandbox** and **Live**. Testing numbers belong in active development projects.

Choosing **Go live** for a Sandbox project opens the production enrollment
checklist. Add the public business and support details, select the expected
message types and volume, describe how recipients opt in, confirm that consent
can be verified, and meet the credit requirement shown in Checkout. The
project becomes **Live** after the checklist and funding requirements pass.

Use separate projects when you need isolated sessions, project credentials,
webhooks, or integration settings. A project token is bound to one project and
cannot authorize access to another project's resources.

## Public management operations

| Resource       | Operations                                                                                  |
| -------------- | ------------------------------------------------------------------------------------------- |
| Organization   | `PATCH /v1/organization` — verified dashboard bearer                                        |
| Projects       | `GET /v1/projects`, `POST /v1/projects` — organization key or verified dashboard bearer     |
| Members        | `GET /v1/members` — organization key or verified dashboard bearer                           |
| Member changes | `PATCH /v1/members/{memberId}`, `DELETE /v1/members/{memberId}` — verified dashboard bearer |

These operations reject project tokens. Use the generated [Platform API
reference](/api/platform-api) for exact request fields, response types,
authentication, roles, scopes, and errors.

## Where to go next

<Columns cols={2}>
  <Card title="API keys" icon="key" href="/console/api-keys">
    Choose an organization key or project token.
  </Card>

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

  <Card title="Billing" icon="credit-card" href="/console/billing">
    Review team plans and number tiers.
  </Card>

  <Card title="Platform API" icon="gear" href="/api/platform-api">
    Inspect public organization and project operations.
  </Card>
</Columns>