Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.
teams
What it is
Part of account/workspace management — team membership, invites, roles,
CRM/analytics settings, and the macro.teams lifecycle event producer that
other features (billing, CRM) subscribe to. See README.md for the full
event contract (schema, sanitization, delivery semantics).
Start here
src/domain/team_service.rs: the main service — creation, invites, membership, role changes, auto-join-domain toggle. Team-wide settings (default link share, interface language) are fields onPatchTeamRequest.src/domain/team_service/invite_link.rs: the team's shareable invite link (TeamInviteLinkService) — who may see, create, reset, or turn it off, and joining through it via the same direct-join path as domain auto-join.src/domain/domain_notice.rs+join_announcement.rs: the one-time email a new work-domain team sends to the creator's same-domain contacts who are not on Macro yet (POST /team/domain-notice, at most 25 per team). Its unsubscribe link is signed by the notification service at send time.src/domain/team_service/invite_reminders.rs+src/inbound/invite_reminder_worker.rs: reminder emails for unanswered invites, swept hourly inauthentication_service. The repository claims due invites and counts the reminder before sending, so replicas never double-send and a failed send drops that reminder rather than retrying.src/domain/invite_rewards.rs: theInviteRewarderport, called when an invite is accepted or someone joins through an invite link (rewarding the sender orteam_invite_link.created_by). Billing implements it inauthentication_service;teamscannot depend onai_billing.src/domain/owned_entity_cleanup.rs+open_seat_release.rs: account/team deletion side effects (owned-entity transfer, seat release).src/inbound/axum_router.rs/src/inbound/toolset.rs: HTTP routes and AI tool surface.src/outbound/team_repo.rs: the Postgres repository; reads use the supplied pool.src/domain/team_repo.rs: reuseget_user_teamsfor viewer teams andget_all_team_membersfor team membership, including owners.
Scope
- Owns: the
"Team"table's lifecycle, membership, invites, and themacro.teamsKafka producer. - Not here: billing/seat pricing logic →
crates/ai_billing(consumes this crate); CRM company/contact sync →crates/crm(this crate only enqueues).
Boundaries
- Depends on:
entity_access,contacts(featureoutbound),channels(featurebackfill_binary),analytics_client,ai_toolset(featureai_tools). - Used by:
services/authentication_service,services/document_storage_service,services/calendar_service,services/agent_harness_service,services/agent_harness_service,crates/scheduled_action,crates/ai_tools,crates/ai_billing,crates/calendar_scheduling.
Recipes
- Add a team mutation:
src/domain/team_service.rs→src/domain/events.rs(new event variant, if it should publish) →src/outbound/team_repo.rs→src/inbound/axum_router.rs. - Repair missed teammate DMs:
just crates/teams/backfill_teammate_dms_local(see README's "Delivery semantics" for when this is needed).
Gotchas
A trialing subscription that gains its first Max seat ends the trial and starts a new billing cycle immediately. Every other seat change keeps the trial, including on a subscription already trialing on Max, so its scheduled downgrades still apply at the trial's end.
Team routes resolve the caller's current team from the principal. A client holding a team (the SDK's
Teamhandle) passes it asteam_idtoPOST /team/inviteandGET /team/invites, andis_expected_teamanswers 409 in that same request when it is no longer the caller's team; withoutteam_idthe routes act on whatever team is current.Invite and reminder emails carry the inviter's display name (
TeamRepository::get_user_display_name). A failed lookup is logged and the email falls back to the inviter's address, so it never blocks an invite.team_invite.is_agentmakes an address with no account sign up as an agent.authentication_service's agent setup joins the team, so the seat is added without a separate acceptance. Existing accounts accept like any other invite. Its email links to the agent signup page (/app/signup/agent?team_invite=<id>).
Checks
cargo test -p teams(SQLX_OFFLINEunset).After query changes:
nix develop --command just prepare_dbfrom the repo root inside Nix.Registered external chats are human-owned; owned-entity cleanup treats their dependency order like other conversations.
Related
- Docs:
crates/teams/README.md· Rules:.agents/rules/rust/db.md