Skip to content

April 12, 2026: Beta access guide and rollout pack

  • Added a reusable beta rollout playbook for code-based access, extensions, revocations, and rollback decisions.
  • Added product-ready beta copy for redemption, welcome, feedback, follow-up, and expiration flows.
  • Published a beta access guide that explains how invited access works and what support needs when a user reports a bug.
  • Clarified that beta codes unlock access while public issue reference codes follow the ERR-XXXXXX format and trace product issues.
  • Added server-side beta rollout flags with cohort, source, beta-tester targeting, deterministic percentage rollout, JSON config payloads, and an emergency kill switch.

Beta rollouts work better when access, support, and product copy all say the same thing. These updates make it easier for customers to understand what beta access means, easier for support to ask for the right code, and easier for internal teams to widen or pause a rollout without inventing new language each time.