Inbox Ownership and Auto Rules How to make sure incoming mail has an owner, and how automatic rules act on it when it arrives.

An address that routes correctly into a queue nobody watches is worse than no address at all - the sender believes they have reached you. This is how to make sure that does not happen.

Ownership

Each area's inbox is owned by that department's manager, taken from your department structure rather than set separately here.

To change who owns an inbox, change the department's manager. To give an inbox an owner it does not have, give the department a manager.

The surface shows each department alongside its manager, so a department with no manager is visible at a glance. Fix those first - it is the single highest-value thing on this page.

Auto Rules

Rules that act on mail when it arrives in an area's inbox. Each rule has a name, an event it responds to, whether it is enabled, and a count of how many times it has fired.

The fire count is the useful number. A rule enabled six months ago with a count of zero is not doing what you thought - either the event never occurs, or the rule does not match. A rule with a very high count relative to your mail volume is probably matching more than intended.

Review the counts periodically. It takes a minute and it is the only honest signal about whether your rules work.

Designing Rules That Hold Up

• One rule, one job. A rule that classifies and assigns and notifies is three rules wearing a coat, and when it misbehaves you cannot tell which part failed.
• Start disabled. Create the rule, look at what would match, then enable.
• Name it for what it does, not when you made it. "Route invoices to Finance" beats "New rule 3".
• Prefer few rules. Every rule is a thing that can silently stop matching when the incoming format changes.

The Whole Chain

When mail arrives, this is the sequence:

Mail sent to your branded address → forwarded by your provider → received by the platform → matched to an alias → filed into the area's inbox → auto rules run → the owner sees it

A break at any point looks the same from outside: nobody replied. Work the chain in order when diagnosing, and check the alias's last-used timestamp first - it cleanly separates "never arrived" from "arrived and was not handled".

A Health Check Worth Running Quarterly

1. Every department has a manager.
2. Every alias has been used recently. An unused alias is either unpublished or not forwarding.
3. Every enabled rule has a non-zero fire count.
4. Send one test message to your most important address, from outside.

Common Questions

Can I assign an inbox to someone who is not the department manager? Ownership follows the department manager by design, so responsibility matches the org structure rather than drifting from it. If the wrong person is managing the queue, the department structure is the thing to fix.

A rule stopped firing. Something about the incoming mail changed - a sender's format, a subject line convention. Rules match on what arrives, and what arrives is outside your control.

Do auto rules replace automations? No. These act on mail as it arrives. Full workflows live in the Automation Hub and can do considerably more. See Building Your First Automation.

Who sees the mail? People with access to that area. Routing to an area is an access decision as much as a filing one.