Organize your workspace
Create projects to separate applications and integrations. Each project has its own domains, API keys, emails, templates, webhooks and marketing resources. Usage and suppressions are shared at account level.
Creating, renaming and deleting projects requires a verified owner or administrator session, or an eligible account token acting as that member. Projects with resources or history cannot be deleted through the normal project deletion flow.
Invite a teammate
Use the project's team settings to invite a colleague and choose the available role appropriate to their work. They accept the invitation using their own account. Member permissions are enforced for dashboard sessions, account tokens and connected agents.
Use a send-only key for application sending and a management key only for trusted administration. A project key does not grant account membership or billing permissions. See authentication.
Assign mailbox access separately
Mailbox access is explicit, even for owners and administrators. In Inbox → Manage → Assign mailboxes, assign only the members who should read each inbox. Creating a mailbox assigns its creator. Administrators can manage mailbox addresses and assignments without reading unassigned messages.
These assignments apply to search, unread counts, attachments, drafts, sent mail, forwarding, exports, API keys, MCP and private webhook events. Removing a mailbox grant also clears forwarding rules for that mailbox.
Remove access
Remove a teammate from project access when their work ends. Revoke unused keys, tokens and OAuth connections. Recreate a webhook with an appropriate member-owned credential if ownership changes; private deliveries require that owner's current mailbox and project access.