Shared macro libraries, without shared exposure.
Makro for Teams is in build. Put your team's canned replies, clinical templates, sales plays, or code-review snippets on a shared shelf - without handing the content to a vendor that can read it. The core product stays zero-knowledge; team packs inherit the same encryption model.
What we are actually building.
The feature set below is the current working plan, not a roadmap promise. Things will change based on what early teams tell us. We'll call out what ships and what gets cut as we go.
Curated macro collections pushed to every team member's extension. Personal macros stay private and take priority if there is a hotword conflict. Packs are read-only for members; the manager controls content.
Browser-based portal for managers. Upload a pack, assign seats, remove a departed member in one click. Runs on Cloudflare Pages; auth via a hashed licence key, same as the current sync flow.
The server stores encrypted pack blobs; it never sees plaintext. Same AES-256-GCM / PBKDF2-600k primitives as the personal sync. No BAA, no covered-entity status - the architecture is what supports compliance, not a certificate.
Let a team define a writing voice that constrains Smart Rewrite outputs for everyone on the plan. Still in research; not committed to ship.
Per-macro anonymised usage rollups for compliance teams. Local-only aggregation, opt-in, no content ever leaves a member's device.
Google Workspace and Microsoft Entra as the first identity providers, then SCIM provisioning for larger orgs. Depends on whether teams on the list ask for it.