Use cryptographically secure public tokens

Understand how public links and tokenised actions use secure unpredictable token generation.

What this guide covers

Understand how public links and tokenised actions use secure unpredictable token generation. The workflow below follows the supported application or module flow and does not invent a menu or bypass validation.

Exact step-by-step process

1. Use the supported Britixo CRM release or workflow that produces this security control.
2. Verify the expected protection through an authorised test.
3. Record the result in the deployment or security audit evidence.

Fields, choices and supported possibilities

• System-generated token
• Linked public action

Code-backed validations and workflow rules

• Tokens are generated by a cryptographically secure source.
• Use the generated link exactly as issued and revoke the underlying public action when access should end.
• A public token is a credential and must not be exposed in logs or unintended communications.

Expected result and verification

• The protection is active without weakening another security control.

Security, audit and troubleshooting checks

• Use the exact authorised account, role and record before saving or sending.
• Verify the saved status and downstream record; a browser success message alone is not sufficient evidence.
• Never expose passwords, API keys, access tokens, protected attachments or raw server paths in support tickets.
• Do not edit module or core database records directly to bypass validation, permissions, migrations or state rules.

Related guides