Shared inboxes are great for collecting requests, but they are usually poor at preserving context. Important decisions disappear in threads, attachments become hard to find, and team handovers depend on who remembers what.

This guide shows a practical way to make incoming emails visible and searchable in Confluence using mailto.wiki — without replacing your normal email workflow.

Disclosure: We are the makers of mailto.wiki, so this post is based on how teams use the product in real customer scenarios.

What this setup solves

• Incoming team emails become Confluence pages or blog posts
• Requests are routed into the right spaces automatically
• Knowledge stays searchable for support, product, and ops
• Handover friction drops because information is centralized

20-minute setup walkthrough

1) Install and open configuration

Install mailto.wiki – Email for Confluence in Confluence Cloud and open the app configuration page from Confluence administration.

2) Register your first email address

Create your first mailto.wiki address (for example, a dedicated address for a single team flow). Save settings and verify registration succeeds.

3) Set default space and content type

Choose a default Confluence space and decide whether incoming emails should become pages or blog posts.

4) Send a test email

Send one test email and verify it appears in the target space. If it does not, check permissions and spam settings first.

Move beyond default routing with Space Rules

Once the basic path works, add rules to route by subject, sender, or recipient patterns.

• Move to: final destination (stops further rule evaluation)
• Copy to: create additional copies (including default destination if applicable)
• Optional: create under a parent page and auto-apply labels

Permissions and spam controls to set early

• Grant app access for protected spaces where needed
• Use safe sender list settings for trusted inbound paths
• Use stricter spam handling only after testing false positives

A practical first rollout plan

1. Start with one team flow (for example: support intake)
2. Run for one week with simple routing
3. Add labels and parent-page routing in week two
4. Scale to additional inboxes after team feedback

Final thought

You do not need a massive migration project to reduce inbox chaos. In most teams, one reliable email-to-Confluence flow is enough to prove value quickly.

If you want, we can publish a follow-up checklist with exact rule templates for Support, HR, and Operations.