Departments

Team collaboration alone gives every editor and viewer the same view of the account: every project, every shared mailbox. That's fine for a small team, but stops being fine once "team" means separate functional groups — support, sales, marketing — with no business reading each other's campaigns or customer threads. Departments add that scoping on top of the existing owner/editor/viewer roles, without changing what those roles can do.

Creating departments

From Settings → Team, the account owner can create departments (Support, Sales, Marketing, or whatever fits) and assign each teammate to one or more of them. A teammate assigned to zero departments keeps seeing every project — departments are opt-in scoping, not a restriction applied by default.

What a department scopes

• Projects — a project can be tagged with one or more departments when it's created. A teammate assigned to a department sees only projects tagged with a department they belong to; the account owner still sees everything, tagged or not.
• Shared mailboxes — an inbound mailbox address (like support@ or sales@) can be scoped to one department, visible to every member of it plus the owner. See Individual vs. shared mailboxes below.

A project or address with no department set stays visible to the whole account, exactly as it worked before departments existed — nothing already built becomes invisible when you turn this on.

Department leads

Assigning a teammate the lead role on a department lets them invite new teammates directly into that department, and rename it, without needing the account owner every time. A lead's reach stops at their own department: they can't invite into a department they don't lead, can't touch billing or credentials, and can't promote anyone else to lead. Everything else that stays owner-only — SMTP settings, Stripe Connect, API keys, webhook secrets, team management itself — stays owner-only for a lead too.

Individual vs. shared mailboxes

Once departments exist, a claimed mailbox address (Inbound mailbox) can be set to:

• Shared — visible to every member of the address's assigned department, plus the account owner. This is the default for an address with no visibility set.
• Individual — assigned to one specific teammate, and private to them. A colleague in the same department, or even the account owner, can't casually open it.

An individual mailbox uses a company-owned address for real work correspondence — it isn't a personal inbox in the legal sense, so the owner isn't locked out of it entirely. Instead, opening someone else's individual mailbox goes through Owner access: the owner picks the mailbox, gives a reason, and only then can read it — read-only, no replying on the assigned member's behalf. That access is logged, and the log is visible to the mailbox's own assignee afterward, not hidden from them. It exists for real business-continuity cases — a departed employee's mailbox, a compliance hold — not everyday browsing.

The disclosure notice

Because department membership changes what a teammate can see, and because owner access into an individual mailbox is possible, anyone accepting a team invite sees a short notice explaining both before they join — what their department makes visible, and that owner access is always reason-required and always logged. Accepting the invite means acknowledging that notice.

Nothing changes if you don't use it

An account with no departments created behaves exactly as Team collaboration already describes: every editor and viewer sees every project and every shared mailbox. Departments are additive scoping you opt into as the team grows, not a new default.