Organization
Manage your whole Organization from the dashboard.
One account can hold several organizations with independent workspaces, so you can run multiple businesses.
Workspaces
Everything stays separate
| Surface | Scoped to |
|---|---|
| Mailboxes & aliases | One organization |
| Companion policy | One organization |
| Calendar & tasks | One organization |
| API keys | One organization |
Create an organization
- 1
Go to Settings → Organization
Click "Create organization" and name the business.
- 2
Add a logo and timezone
These show up on the workspace switcher and mail notifications.
- 3
Connect the first inbox
Each org starts empty. Mailboxes and Companion policy do not carry over.
Switching between them
The header switcher lists every workspace you are in. Pick one and mailboxes, calendar, tasks, and settings reload for that org.
A retail brand and a SaaS product under the same account stay fully separate — aliases, Companion policy, and keys included.
Team members
- 1
Go to Settings → Organization → Members
- 2
Enter their email and pick a role
- 3
They accept from the email link
- 4
They show up in assignee dropdowns and @mentions
Roles
| Role | What they can do |
|---|---|
| Owner | Everything, including deleting the org |
| Admin | Inboxes, Companion policy, API keys, and members |
| Member | Mail, calendar, and tasks assigned to them |
| Viewer | Read-only mailbox and analytics |
Fine-tune exactly what each role sees under Access.
Assigning work
Only org members can be assigned mail, calendar events, or tasks. Set a default assignee per alias if you want new threads to route automatically.
Who sees what
Lock dashboard sections by role. People only see what they need.
| Section | What it covers |
|---|---|
| Mailbox | Inboxes, aliases, Companion policy |
| Calendar & tasks | Events and assigned work |
| Developers | API keys and MCP |
| Analytics | Usage metrics |
| Settings | Organization and members |
API keys
A key belongs to one organization. Rotate anytime under Settings → API keys.
Privacy
- TLS 1.3 for everything in transit
- Each tenant is isolated at the database level
- Hashed user IDs so no raw PII is needed
- Domain allowlists on scoped keys