1. What This Feature Does
The Restrict File Extensions setting allows administrators to block specific file types from being uploaded across the entire TitanFile subscription.
This helps prevent the upload of potentially unsafe or non-compliant file types (e.g., .exe, .bat, .js), reducing security risks and ensuring adherence to organizational policies.
You can define:
- Which file extensions are restricted from being uploaded
- A list of commonly restricted extensions to quickly apply standard security practices
2. Who Can Use It
- Admin users can configure file extension restrictions
Plan-Based Behavior
For All Plans (Enterprise and Non-Enterprise)
- This setting is enforced globally across the entire subscription
- When configured, restrictions apply to all users and all channels
- There is no Manage Roles control for this feature
- Users cannot override these restrictions
Important:
- This is a hard enforcement setting
- If a file extension is restricted, it cannot be uploaded anywhere in the system
3. Step-by-Step Instructions
- Navigate to Security Settings
- Locate the Restrict File Extensions section
- Enter the file extensions you want to restrict:
A. Enter File Extensions
- Type file extensions separated by commas or spaces
- Do not include a dot (.)
Examples:
- exe bat js
- exe, bat, js
B. Add Commonly Restricted Extensions
- Click “Add Commonly Restricted Extensions” to automatically populate a list of commonly blocked file types
Changes are applied immediately once extensions are entered or updated. There is no Save button.
4. What Happens After
- All specified file extensions are blocked across the entire system
- Users will be prevented from uploading restricted file types in any channel
- The restriction applies immediately after configuration
Important Behavior
- Restrictions apply to:
- File uploads in channels
- Any feature that supports file uploads
- If a user attempts to upload a restricted file type:
- The upload will be blocked
- An error message will be displayed
- Restrictions apply universally:
- No role-based exceptions
- No channel-level overrides
5. Best Practice
For effective security management:
- Restrict high-risk file types such as:
- exe, bat, cmd, js, msi
- Use “Add Commonly Restricted Extensions” as a baseline
- Regularly review and update restricted extensions based on organizational policies
This ensures:
- Reduced risk of malicious file uploads
- Improved compliance with security standards
- Consistent enforcement across all users and channels