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

# Account settings

> Account, workspace, and API key settings overview

## What this page helps you do

Find and manage your account-level settings. This page points you to the right place for profile, team, API keys, signatures, and brand configuration.

## Before you start

* A Nudgen account
* Owner or admin role for workspace-level settings

## Settings overview

Go to **Settings** in the dashboard to access:

| Section        | What you can do                                                           | Doc                                                           |
| -------------- | ------------------------------------------------------------------------- | ------------------------------------------------------------- |
| **Team**       | Invite members, assign roles, manage permissions                          | [Team settings](/en/settings/team)                            |
| **Brand**      | Set brand identity: name, description, reply-to email, logo               | [Brand identity](/en/settings/brand)                          |
| **API Keys**   | Create and revoke Personal Access Tokens for REST, MCP, and CLI workflows | [Developer API](/en/agents/api), [MCP server](/en/agents/mcp) |
| **Signatures** | Create and edit email signatures for campaigns                            | [Signatures](/en/settings/signatures)                         |

## Workspace and account

Your account can belong to **multiple workspaces**. The **active workspace** is shown in the sidebar header; use the team switcher to change it. Contacts, campaigns, brand settings, billing, and API requests are scoped to the active workspace. Your profile is account-level and used for test emails, team member display, and activity.

## API keys

Use **Settings -> API Keys** to create Personal Access Tokens. PATs authenticate the Developer API, MCP server, and CLI. Copy a token once when it is created, store it securely, and revoke it when a script or agent no longer needs access.

<Warning>
  Treat PATs like passwords. They can create contacts, update brand settings, create campaigns, and launch real email depending on your workspace permissions and plan.
</Warning>

## What happens next

* [Developer API](/en/agents/api) - use PATs with REST endpoints.
* [MCP server](/en/agents/mcp) - connect Nudgen to MCP-capable agents.
* [Manage your team](/en/settings/team) - invite collaborators and set roles.
* [Set up signatures](/en/settings/signatures) - add signatures to campaign emails.
* [Configure brand tone](/en/brand/overview) - control how AI generates content.

## Related docs

<CardGroup cols={2}>
  <Card title="Developer API" icon="code" href="/en/agents/api">
    REST access with API keys.
  </Card>

  <Card title="MCP server" icon="bot" href="/en/agents/mcp">
    Tool-based agent access with API keys.
  </Card>

  <Card title="Team settings" icon="users" href="/en/settings/team">
    Invites, roles, and permissions.
  </Card>
</CardGroup>