# Company email and team access

Create a company-domain mailbox, connect team access and bring its customer conversations into Bow Chat.

## Company email in the business workspace

A functional address such as `sales@example.com` belongs to the company rather than one employee. Boni joins its mailbox, authorized company members and outgoing identity, and can connect the same email address to Bow Chat.

Company email is distinct from [Email CPaaS](/communications/email): a mailbox supports correspondence and threads; CPaaS provides sender domains, templates, campaigns and delivery events. Both use the company's authorized sending identity.

## Set up the company service

An authorized company administrator opens **Mail Domains & Mailboxes** in [Boni Panel](https://panel.boni.one), in the company that owns the domain.

| Action | Use it for |
|---|---|
| **Verify domain ownership** | Prove control through the supplied TXT record while keeping existing website and mail services |
| **Create company email** | Set up the incoming mailbox, company access and outgoing service |
| **Put email in Bow Chat** | Connect an existing company mailbox to its customer inbox |
| **Set up email and Bow Chat** | Run the mailbox and Bow connection as one setup process |

Full DNS delegation is the separate [Domain Management](/domains/connect-your-domain) workflow. A TXT ownership check alone does not move the domain's current mail or website.

Review the saved setup operation and any required action. Keep the same setup when continuing or recovering it, so the company retains its mailbox and connected inbox.

## Give the right people access

The company mailbox uses the selected membership and sharing policy. New functional mailbox setup supports company-administrator access; explicit company grants and exclusions can define the intended team. Review access as people join, leave or change responsibility.

People use their own Boni identity to reach authorized services. Connecting a mailbox to Bow Chat also needs a compatible Bow access policy: Bow administrators can access the account's inboxes, so choose that audience deliberately.

## Check the complete journey

After setup, verify a real external email reaches the intended mailbox and connected Bow inbox. Reply on that thread and confirm the recipient receives it. For human Mail use, also check ordinary sign-in and the saved Sent item. Sender configuration, provider acceptance and recipient delivery are separate checks.

## Continue the relationship

Use [CRM](/crm/overview) for the customer record and [Tasks](/tasks/overview) for the next commitment. Bow Chat keeps the email conversation with the team handling it. See the [business email module](https://boni.one/platform/business-email) for how these pieces fit together.

Canonical: https://docs.boni.one/mail/company-email
Version: 1
Updated: 2026-10-09T06:20:30.400Z