Verify the updated future-tenant database seed

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Confirm newly provisioned SaaS tenants receive the hardened baseline.

What this guide helps you do

Confirm newly provisioned SaaS tenants receive the hardened baseline. The workflow below follows the supported application or module flow and does not invent a menu or bypass validation.

Follow these steps

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

Fields and options

• Updated future-tenant database seed

Rules and limits

• Provision a controlled test tenant through the supported workflow.
• Verify the required security schema/defaults are present.
• Remove the test tenant through the authorised lifecycle after validation.
• Do not use a copied live customer database as an informal seed.

Check it worked

• 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