> For the complete documentation index, see [llms.txt](https://copilot-docs.bugbase.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://copilot-docs.bugbase.ai/enterprise/settings/email-identities.md).

# Email Identities

Manage monitored test inboxes, their account and access notes, and how vetting uses them.

Email identities are workspace-scoped inboxes that Pentest Copilot can use for sign-up, email OTP, invitation, and magic-link flows. Each identity has a label, a unique email address, and optional notes describing the accounts and access associated with it.

## Add account and access notes

1. Open **Settings -> Email Identities**.
2. Find the identity you want to document.
3. Enter the details under **Account & access notes**, directly below the identity's email address.
4. Click **Save notes**, or press **Ctrl/Cmd + Enter**.

Notes can also be entered while creating an identity. Clear the text and save to remove existing notes.

Use a simple service-by-service format so your team can understand the account:

```
Google
Email: test-admin@example.com
Password: <test password>
Role: Workspace administrator

GitHub
Username: test-admin
Password: <test password>
Organization access: Example Security
```

Notes accept up to 10,000 characters.

{% hint style="warning" %}
Notes may contain credentials. Store only assessment-specific test access, keep workspace membership restricted, and remove credentials when they are no longer valid.
{% endhint %}

## Use notes in browser sessions

When you select an identity in **Browser Session Manager**, its **Account & access notes** appear immediately below the **Email Identity** selector. If the identity has no notes, the manager shows an empty-state message that points you back to the settings location.

Reopen Browser Session Manager if it was already open when the notes changed.

## Use identities with AI configure

[AI configure](https://copilot-docs.bugbase.ai/enterprise/how-to-trigger-a-web-assessment/ai-configure-and-vetting.md) uses your workspace's email identities in two ways:

* **Email codes for your accounts.** When an account in **Accounts** gets a sign-in code by email, use one of these identities as the account's email address. Vetting reads the code from that inbox.
* **Self-signup.** When you turn on **Self-signup** in **Scan settings -> Access**, vetting creates accounts through your site's sign-up flow with these identities, and they receive the verification emails and codes.

With **Self-signup** on, **Available identities** lists every identity that is not archived, with a **Copy** button for each address. Paste an address into **Accounts** to say which identity to use for a role:

```
Role 2: member, sign up with <identity address>
Role 3: seller, sign up
```

Without an address, vetting picks an identity at random. If the workspace has no identities, the list says so; add them on this page.

{% hint style="info" %}
If verification emails do not reach the identities, vetting lists it under things to fix. Allow mail to the identity addresses, or give accounts that are already verified.
{% endhint %}
