Apply upload and installer web-server protections

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

Protect uploaded content and installer locations from direct execution or unsafe public access.

What this guide helps you do

Protect uploaded content and installer locations from direct execution or unsafe public access. 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

• Upload paths
• Installer paths
• Execution/direct-access restrictions

Rules and limits

• Deploy the supplied web-server protection files.
• Verify scripts cannot execute from protected upload paths.
• Serve uploaded files only through authorised application routes.
• Lock or remove installer access after the supported installation or upgrade.

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