⚠️ Every key generated here is a real token. Test keys must use channel 0x00 (TEST). Production keys use channels 0x01–0x09. All generation events are logged to the append-only audit log.
Single Token
Scope
Channel
Duration (days, blank = perpetual)
Generation
Token Generated SUCCESS
Redemption Token
—copy
Token Hash
—copy
Batch ID
—copy
QR Code URL
QR URL see below
—copy
Batch Generation
Scope
Channel
Batch Size
Duration (days, blank = perpetual)
Generation
Batch Generated SUCCESS
CSV contains all token strings, hashes, and QR URLs. Store securely — tokens cannot be retrieved again.
Batch Registry
All issued batches — redemption status and management
Test channel tokens (0x00) are highlighted. Use "Clear Test Data" to void all test entries after testing is complete.
📦
Loading batches…
fetching from burn registry
Batch
Loading…
Audit Log
Immutable record of all system events
Event Type
Limit
📋
Loading audit log…
Key Verify
Decode and validate any Redemption Token or Operating Key
Token Verification
Paste Redemption Token or Operating Key
Verification Result
Staff
Staff account management — T0 only at launch
Only T0 (Owner) at launch. Staff accounts will be created here when the first CCRs are onboarded after BP launch.
Add Staff Account
Email address
Display name
Tier
Primary Scope
Notes (reason for account creation — required)
After saving: you must manually add this email to Cloudflare Access. The button below copies the email and opens the CF Access page.
Current Staff
Name
Email
Tier
Scope
Status
Created
T0 only at launch
Staff accounts appear here when created
Cloudflare Access Guide MANUAL STEP REQUIRED
After creating a staff account above, add them to Cloudflare Access:
1. Go to Zero Trust → Access → Applications → admin.myhealthlog.app
2. Edit the policy → Add Include rule: Email → enter the staff email
3. Save the policy
4. The staff member will receive a Cloudflare Access invite on their next login attempt
⚠️ Until step 2-3 is complete, the staff account exists in MHL records but cannot log in.
Error Log
Client-side errors captured this session — clears on page reload
Errors are captured automatically when any API call or JS operation fails. This log is session-only — it clears on reload. Use Copy All to share with development.
✓
No errors this session
Announcements
System, scope, and cross-scope messages — three-level scoped
Three levels: System (T0 → all staff) · Scope (T2+ → their scope) · Cross-scope (T1 → selected scopes). Urgent announcements require acknowledgment before dismissal.