Understand denied attachment extensions

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

This guide explains that security deny-list.

What this guide helps you do

Know security deny-list. The workflow below follows the supported application or module flow and does not invent a menu or bypass validation.

Follow these steps

1. Go to the exact navigation path shown above.
2. Select the authorised mailbox, message or configuration record.
3. Complete the fields or action described in this guide.
4. Save or submit once, then verify the resulting status and related record.

Fields and options

This workflow does not expose additional user-entered fields.

Rules and limits

• Denied includes php/phtml/pht/phar/cgi/pl/py/rb/sh/bash/zsh/js/mjs/html/htm/xhtml/shtml/htaccess/ini/env/log/exe/dll/so/dylib/com/bat/cmd/msi/jar/ps1/vbs.
• Unknown unsafe names can become .bin.
• Deny-list applies even with broad allow-list.

Check it worked

• The requested Mailbox Exchange record is updated through the supported controller and remains attributable to the acting staff member.

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