Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.
Authentication Service Configuration
Development signup allowlist
Temporary open signup override
Develop currently allows every public signup, even when
DEVELOPMENT_BYPASS_SIGNUP_ALLOWLIST is false or absent. The temporary override
in Config::signup_policy_for_environment skips the allowlist for both runtime
startup and Doppler validation. Production and Local behavior is unchanged.
Deploy the authentication service to apply this change. To restore allowlist
enforcement, remove the temporary override, confirm the Develop allowlist is
valid and the bypass flag is false, and redeploy. Changing Doppler alone cannot
disable this override. Existing accounts remain after enforcement is restored.
The configuration behavior described below applies once the override is removed.
The authentication service gates new signups with a startup-built SignupPolicy.
The policy is enforced authoritatively by the existing FusionAuth user.create
webhook at /webhooks/user. FusionAuth is configured for user.create with
AbsoluteMajority, so a non-2xx response from this service rejects the
transaction and aborts FusionAuth user creation.
Public prechecks in user creation and passwordless signup exist only for a
faster user-facing 403 response. They are advisory. The transactional webhook
is the enforcement boundary for all signup paths, including SSO and future
FusionAuth-created users.
Settings
- Doppler project:
authentication-service - Develop Doppler config:
dev - Production Doppler config:
prd
| Setting | Format | Default |
|---|---|---|
DEVELOPMENT_SIGNUP_ALLOWLIST_JSON |
JSON array of exact email-address strings | No default |
DEVELOPMENT_BYPASS_SIGNUP_ALLOWLIST |
Exactly true or false |
false when absent |
Synthetic allowlist example only:
["[email protected]", "[email protected]"]
Do not commit or paste operational allowlist values into source, docs, logs, PRs, or generated files.
Environment behavior
| Runtime environment | Doppler slug | Bypass | Effective signup policy |
|---|---|---|---|
Environment::Develop |
dev |
Off | Requires DEVELOPMENT_SIGNUP_ALLOWLIST_JSON to be present, nonblank, valid, and non-empty. |
Environment::Develop |
dev |
On | Allows all public signups. The allowlist setting is ignored even if missing or malformed. |
Environment::Production |
prd |
No effect | Allows all public signups. The allowlist setting is ignored even if present or malformed. |
Environment::Local |
lcl |
No effect | Allows all public signups. The allowlist setting is ignored even if present or malformed. |
With the bypass off, Develop startup fails if the allowlist setting is missing, blank, malformed JSON, not a JSON array, empty, contains a non-string entry, contains a blank entry, or contains an invalid email address. With the bypass on, Develop neither requires nor parses the allowlist setting, so the bypass takes precedence over any allowlist value. Production and Local do not require the allowlist setting and do not parse it.
The bypass accepts only the exact values true and false. Values such as
True, 1, yes, or an empty string fail startup in every environment,
including Production and Local, where the bypass otherwise has no effect.
Matching and validation semantics
With the bypass off, the service parses the allowlist once at startup and stores it in memory. Request handlers perform hash lookups only.
Normalization rules:
- Trim leading and trailing whitespace from each configured entry.
- Validate each entry with the service email parser.
- Lowercase the address after validation.
- Deduplicate normalized addresses.
Matching rules:
- Matching is exact after normalization.
- Case differences do not matter.
+aliases remain distinct addresses.- Domains, wildcards, suffixes, patterns, and regular expressions are not supported.
- Denial responses and policy errors must not disclose configured addresses.
GTM invite links
Macro staff (any @macro.com account) mint personal, 48-hour signup links from
/app/internal/invite-links. The recipient opens /app/invite?token=…, signs up,
and the account is attributed to the staff member who created the link. At the
plan step of onboarding the account sees a free-month offer instead of the plan
picker, and checkout applies a Stripe promotion code server-side. The Stripe
subscription webhook then marks the link converted.
Both settings are optional plain Doppler values (project
authentication-service); the service falls back to the defaults when unset.
| Setting | Default | Meaning |
|---|---|---|
GTM_INVITE_PROMO_CODE |
1MF |
Customer-facing Stripe promotion code applied at checkout. Must exist and be active in Stripe (1MF is 100% off the first month). |
GTM_INVITE_LINK_TTL_HOURS |
48 |
How long a link can be opened and redeemed after creation. |
Links live in the gtm_invite_link MacroDB table (crate gtm_invite); the
dashboard reads it through GET /gtm-invite/links.
Shared mailboxes
Internal shared-mailbox grant relocation creates ordinary FusionAuth users for
mailbox grants. In Develop with the bypass off, those mailbox addresses must be
listed explicitly in DEVELOPMENT_SIGNUP_ALLOWLIST_JSON before relocation
creates the FusionAuth user. With the bypass on, Develop allows those addresses
like any other signup. Shared mailboxes get no metadata-based exemption from the
signup policy.
Rollout
Configure
DEVELOPMENT_SIGNUP_ALLOWLIST_JSONin Doppler projectauthentication-service, configdev, using only the approved operational addresses for the deployment. Keep values out of source control and chat.Validate the Doppler configs and semantic policy resolution. The validator reads configs
devandprdwith the Doppler token in theDOPPLER_TOKENenvironment variable:nix develop --command cargo run -p authentication_service --bin authentication_service_doppler_configDeploy the authentication service build that contains the signup policy.
Restart or replace all Develop authentication service tasks. The service reads both settings once at startup. Changing Doppler after deployment does not update running tasks.
Confirm Develop signups for allowed synthetic/test accounts succeed and unlisted synthetic/test accounts receive a generic
403without onboarding side effects.
Production and Local remain allow-all and can deploy independently of the Develop allowlist value.
Change the bypass
To allow every public signup in Develop:
- Set
DEVELOPMENT_BYPASS_SIGNUP_ALLOWLISTtotruein Doppler projectauthentication-service, configdev. - Restart or replace all Develop authentication service tasks.
- Confirm that an unlisted synthetic test account can sign up.
To enforce the allowlist again:
- Confirm that
DEVELOPMENT_SIGNUP_ALLOWLIST_JSONlists every non-Macro address that still needs to sign up in Develop, including shared mailboxes. - Set
DEVELOPMENT_BYPASS_SIGNUP_ALLOWLISTtofalsein configdev, or delete it. - Run the Doppler config validator from rollout step 2.
- Restart or replace all Develop authentication service tasks. If the allowlist is missing or invalid, Develop startup fails until you fix it.
- Confirm that an unlisted synthetic test account receives a generic
403.
The validator skips DEVELOPMENT_SIGNUP_ALLOWLIST_JSON while the bypass is on.
The allowlist can become invalid without detection, so validate it before you
turn the bypass off. Accounts created while the bypass is on remain afterward.
Rollback
- If Develop startup fails because of the allowlist, fix the Doppler JSON value and restart the service tasks. The service will not accept traffic until the Develop value is valid. Turning the bypass on also lets Develop start, but Develop then allows every public signup until you turn the bypass off.
- If startup fails because of
DEVELOPMENT_BYPASS_SIGNUP_ALLOWLIST, set it to exactlytrueorfalse, or delete it. Then restart or replace the service tasks. This failure can happen in any environment. - If a legitimate Develop signup is denied, add the address to the Doppler JSON array and restart or replace the authentication service tasks.
- If Develop must stop allowing every public signup, follow Change the bypass to enforce the allowlist again.
- If the release must be reverted, roll Develop back to the previous
authentication service deployment or task definition. Builds from before the
bypass ignore
DEVELOPMENT_BYPASS_SIGNUP_ALLOWLISTand enforce the allowlist, so keep a valid Develop allowlist configured even while the bypass is on.
Focused verification
Useful checks after editing signup configuration behavior:
nix develop --command env -u DATABASE_URL cargo test -p authentication_service --bin authentication_service config::test
nix develop --command cargo check -p authentication_service --bin authentication_service_doppler_config
cargo fmt --check
Review this README and related logs before rollout to confirm they contain only placeholders or reserved synthetic examples, never operational email addresses or copied Doppler values.