Apply Britixo SaaS migration 040

Apply the SaaS database component required by token and tenant hardening.

What this guide covers

Apply the SaaS database component required by token and tenant hardening. 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

• Required SaaS migration number: 040

Code-backed validations and workflow rules

• Deploy the matching Britixo SaaS files.
• Run the supported module/database upgrade.
• Confirm migration 040 completes.
• Test token lifecycle and controlled tenant provisioning.

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