Portal Code Sync

The portal uses access codes (e.g., BANKS, SPONSORS, FAFO-F4M) mapped to audiences and target pages via portal-access.json. This page documents how those codes are kept in sync.

Current Mechanism

• The canonical mapping lives in: /var/www/rr/assets/data/portal-access.json.
• An admin copy lives in: /var/www/rr/admin/api-data/portal-access.json.
• CLI tools such as rr_portal_audit and rr_portal_reset_codemap are used to audit and reset the mapping.

Operational Workflow

1. Propose new code or audience mapping in a change request.
2. Update the canonical JSON at assets/data/portal-access.json.
3. Run rr_portal_audit to confirm there are no broken links.
4. Deploy changes via standard release process.

Future versions of this tool may allow in-browser editing with the CLI still acting as the source of truth for validation and logging.

« Back to Admin Console