Email on your projects

With Google or Microsoft 365 connected, Ambital files client email against the project it belongs to. A project's Emails tab becomes the engagement's correspondence record — every thread with that client, next to the tasks, meetings and money it relates to.

How threads find their project

Routing is rule-based, per project — domain rules ("anything involving @acme.co.uk"), subject keywords, exclusions and label filters, all visible in one place under Settings → Email Routing. The full mechanics, including the sync-all catch-all for dedicated project mailboxes, are in Routing emails and meetings.

Everything else — including your business's own email — is under Inbox → Emails, where you can filter to your own internal project to keep company admin apart from client threads.

Turning an email into a task

The best feature on the tab: when an email contains work ("could you also…?"), create a task from the email right there. The task keeps a link back to the thread that spawned it, and the email shows a chip pointing at its task — so scope arriving by email stops evaporating.

Reading and privacy

Emails shown on a project are the ones involving that project's people — your inbox as a whole is not on display, and what syncs at all is controlled per connected account under Settings → Integrations (see the Integrations overview). Clients never see the Emails tab; it's an operator surface.

If threads aren't appearing

It's almost always routing, not sync: the sender isn't among the project's linked people, or the mail is in an account whose email service isn't enabled. The checklist in Sync and connection problems covers it.

Tip: the email-to-task habit is worth building. Anything a client asks for in prose either becomes a task or politely doesn't — the Emails tab makes the first option two clicks.