Skip to main content

​
Get help

Email support

Write to support@macro.com — include what you were doing and what you expected to happen.

Book a call

A member of our team will walk you through setup or dig into a problem live.

File a bug on GitHub

Macro is open source — bug reports (and pull requests) are welcome on the monorepo.

Watch the demo

Many “how do I…” questions are answered in the product walkthrough.
For specific topics: licensing@macro.com for commercial licensing, self-host@macro.com for HIPAA/FedRAMP and self-hosted deployments, and teo@macro.com if you want to contribute but aren’t sure where to start.

​
Common issues

You don’t have access yet. Ask them to @mention it in a channel you’re both in — that shares it with every member automatically — or to share it with you directly from the item’s Share menu. See Permissions.
Check the Noise tab — Macro filters lower-priority senders out of Signal. If a sender is misclassified, right-click any of their threads to move them between Signal and Noise; the change sticks for future emails. See Signal vs Noise.
That’s by design: mentions in a document’s body don’t notify or share. Mention them in a comment, or share the doc with them explicitly. The reasoning is covered in Mentions.
Two usual causes: some features roll out gradually, so your account may not have them yet — and some features are desktop-only, like splits and keyboard shortcuts. See Apps & platforms.
Calls are shared to team memory by default. During a call, uncheck the toggle in the bottom left to keep it personal — the call still goes to your own memory, just not the team’s. See Calls.
Agents inherit your permissions — if you can’t open it, neither can they. Get access to the item first (see the first question above), then ask again. See Mentions in Agents.
When reporting a bug, include your platform (web or iOS), the block type involved (email, doc, channel, …), and a link to the affected item if you have one — it cuts the back-and-forth in half.