Access codes

Every code issued, what it granted, who minted it, and its state. Manage, audit, and revoke here — the full oversight surface.

Minting happens in the room — reps issue codes from the App's Access codes screen. This is the management half. Open the App ↗

Issued · 30d

across 4 reps

Redeemed

71% redemption

Active trials

Pro, via code

Revoked

unredeemed

Trial ceiling90 days max · server-enforced

Who can mintplatform_admin (audited)

Defaultsingle-use · 14-day expiry

PolicySPEC.org-plan-model.md ↗

Issued codes audit · who minted what

Code	Grants	Use case	Minted by	Issued	State
ACS-K7M2	gatepro 30d	Shopify ops — 3 agents, context dies	erik@relayctx.com	Jun 12	redeemed
ACS-T2HF	gatelooppro 14d	Dev infra eval — PR review handoffs	erik@relayctx.com	Jun 13	issued
ACS-W8DN	gate	Fintech — compliance pilot	sam@relayctx.com	Jun 13	issued
ACS-B6PZ	gatepro 90d	Agency — multi-client workspaces	erik@relayctx.com	Jun 10	revoked

Concept — the Console surface. Pairs with the App's in-room Access codes mint and the split explainer. Both surfaces call one role-gated endpoint — /api/admin/v1/access-codes — over a single service; the App mints, the Console manages. An access code is a beta_codes row extended with grant_loop, trial_days, use_case, source='demo', minted_by; activation reads it instead of hardcoding beta and logs the redemption (pre-cleared + audited). Every grant lands on the prospect's own org — never the rep's. Policy governed by SPEC.org-plan-model.md in relay-board.