Skip to main content

Support email alias — `soporte@tuempresa.digital`

canonical · devops · updated 2026-06-17 · source

Canonical support / product-comms email for the tuempresa.digital domain. Decided to unblock the Google OAuth consent screen (Google login via Clerk in apps/admin), which requires a User support email + Developer contact email that must NOT be a personal account (jose.gutierrez@ramva.com). Also used for general product communications. (Issue #186.)

Decision​

ItemValue
Primary aliassoporte@tuempresa.digital
Forwards toJosé's Google Workspace primary mailbox (the domain's admin/owner mailbox)
Mail providerGoogle Workspace (domain MX = 1 smtp.google.com)
In codeapps/admin/src/components/auth/AuthLayout.tsx — the auth footer "SOPORTE" link already points here (mailto:soporte@tuempresa.digital). This is the single source of truth in the product UI.

Rationale for soporte@ over hola@ / ayuda@: the product UI footer label is "SOPORTE" and the alias is consumed primarily as a support contact (auth screen + OAuth consent screen). One alias is enough for the current scale; add hola@ later only if marketing comms need a separate inbox.

Runbook — external configuration (console access required)​

These steps run in the Google Admin console + Google Cloud Console and cannot be automated from the repo. Owner: José (Workspace super-admin).

1. Create the alias in Google Workspace​

  • Option A — group alias (recommended, no extra license): Admin console → Directory → Groups → create group soporte@tuempresa.digital, add José as the only member, set Who can post = "Anyone on the internet" so external senders reach it. $0, survives if the owning user changes.
  • Option B — user alias: Admin console → Directory → Users → José → Add alternate email → soporte@tuempresa.digital. Simpler but tied to that single user account.

Prefer Option A (group) — it decouples the support address from any one person's account.

2. Verify send / receive​

  • Send an external email to soporte@tuempresa.digital; confirm it lands in the target mailbox.
  • Reply / send from soporte@tuempresa.digital (Gmail → Settings → Accounts → Send mail as) and confirm SPF/DKIM pass on the outbound message (check the received-message headers).
  • Google Cloud Console → APIs & Services → OAuth consent screen (the project backing the Clerk Google login for apps/admin).
  • Set User support email = soporte@tuempresa.digital.
  • Set Developer contact information = soporte@tuempresa.digital.
  • Save; re-verify the Clerk Google login still completes after the change.
  • Clerk + Google OAuth setup (DNS configured, domain verified) — see the admin auth flow in apps/admin/src/components/auth/ and the Clerk memory notes.
  • Resend sender-domain SPF/DKIM/DMARC for transactional email is a separate concern tracked in tedos-devops-plan.md (§ password-reset email sender domain) — do not conflate with this support alias.