Fyxer is built for individual inboxes and calendars, even when used in a team. This article explains what's supported today, what isn't, and how teams typically work around it.
The Short Answer
Shared inboxes and shared mailboxes are not supported.
This includes:
info@, sales@, support@ inboxes
Microsoft 365 Shared Mailboxes
Google Group inboxes
Any mailbox accessed by multiple people
Fyxer connects to one person's inbox and calendar at a time.
What Is Supported
Individual inboxes (recommended)
Each team member connects:
Their own Gmail inbox (Google Workspace or personal)
Their own Outlook inbox (Microsoft 365 / Exchange Online)
Each user gets:
Their own drafts
Their own inbox categorization
Their own meeting notes and summaries
This keeps data private and predictable.
Why Shared Inboxes Aren't Supported
Shared inboxes introduce problems that conflict with how Fyxer is designed to work:
1. No clear ownership
Fyxer needs to know:
Who should receive drafts
Who owns meetings
Whose calendar rules apply
Shared mailboxes don't have a single owner, which breaks this logic.
2. Privacy and security risks
Shared inboxes often contain:
Sensitive client conversations
Internal or financial data
Messages not meant for all users
Fyxer intentionally avoids setups where:
Multiple people can see drafts or notes unexpectedly
Access rules are ambiguous
3. Reliability issues
Shared mailboxes behave differently across platforms:
Permissions vary by admin setup
APIs are limited or inconsistent
Message ownership can't be determined reliably
Supporting shared inboxes would result in:
Missed drafts
Incorrect categorization
Unclear visibility of data
That's a trade-off we've chosen not to make.
Common Expectation Mismatch (and How Fyxer Differs)
Some tools focus on:
Shared call libraries
Centralized team inboxes
Manager-level visibility into all activity
Fyxer takes a different approach:
Individual ownership
Strong privacy boundaries
No "hidden" access to inboxes or meetings
This is intentional - and why Fyxer works best when each person connects their own inbox.
Recommended Workarounds
If your team relies on a shared inbox, here are proven alternatives:
Option 1: Individual inboxes + forwarding
Keep the shared inbox as-is
Forward relevant emails to individual inboxes
Let Fyxer handle drafts and categorization per person
This maintains privacy while still reducing workload.
Option 2: Role-based inbox ownership
Instead of a shared mailbox:
Assign ownership (e.g. sales@ → individual reps)
Rotate responsibility by forwarding rules
Use Fyxer per user
This gives clearer accountability and better results.
Not recommended: Connecting shared mailboxes
Even if technically possible in some environments, this setup:
Is unsupported
Can cause unpredictable behavior
May stop working without warning
Support won't be able to troubleshoot shared mailbox issues.
Planning to Use Fyxer With a Team?
Before rolling out, we recommend:
Confirming each user has an individual inbox
Setting expectations about privacy and visibility
Reviewing Admin vs Member roles
Disabling auto-add domain if you want individual billing
Why This Matters
Most frustration comes from expecting shared visibility where none exists.
Fyxer works best when:
Ownership is clear
Privacy is respected
Each inbox belongs to one person
If shared inbox support is critical for your workflow, Fyxer may not be the right fit today - and that clarity upfront is intentional.