Confirm removal of unnecessary runtime development artefacts

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

Verify that development-only material is absent from the production runtime overlay.

What this guide helps you do

Verify that development-only material is absent from the production runtime overlay. 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

• Approved production runtime manifest

Rules and limits

• Compare the deployed runtime with the approved release manifest.
• Verify unnecessary development artefacts are absent while required dependencies, migrations and protection files remain.
• Do not delete files based only on filename guesses.

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