This guide will walk you through the Uploading settings page in your BeDesk admin area. Properly configuring these settings is crucial for managing how files are stored, their size limits, and the types of files your users and agents can upload in tickets, livechat and help center.
This section is where you decide where all uploaded files are stored. BeDesk provides several options, from local server storage to various cloud providers.
User Uploads Storage Method: Choose the default storage location for all user-generated files, like ticket attachments. The available options are:
Local Disk (Default)
FTP
DigitalOcean Spaces
Amazon S3 (or any S3-compatible service)
Rackspace
When you select any provider other than Local Disk, a new panel will appear below, prompting you to enter the necessary credentials (like API keys, secrets, region, and bucket/container name) to connect to that specific service.
To enhance performance and reduce the load on your server, you can enable direct uploads.
Enable direct upload: When this option is checked, files are uploaded directly from the user's browser to your chosen cloud storage provider, bypassing your server entirely. This results in faster uploads and less server resource consumption. 🚀
CORS Configuration: For direct uploads to work, you must configure Cross-Origin Resource Sharing (CORS) settings with your storage provider. This allows the provider to accept uploads originating from your BeDesk domain.
This setting optimizes how large files are delivered to users for download, reducing your server's memory and CPU usage.
File Delivery Optimization setting is only relevant when upload provider is set to Local. If it's set to s3 or something else, files will be delivered directly from that storage provider.
None: The default method, where your server streams the file.
X-Sendfile (Apache): If your web server is Apache, select this option to have Apache handle file delivery directly after authorization.
X-Accel (Nginx): If your web server is Nginx, use this option to let Nginx manage the file download.
You must have the corresponding module (mod_xsendfile for Apache or X-Accel for Nginx) enabled on your server for these optimizations to work.
Here you can define the limits for file uploads and storage space. Note that all values in these fields are set in bytes.
Chunk Size: This setting allows you to upload large files in smaller pieces or "chunks." This is useful for getting around server limitations on maximum file upload sizes (like PHP's upload_max_filesize).
Maximum File Size: This sets the absolute maximum size for a single file that a user can upload.
Available Space: Define the total disk space each user is allocated for their uploads. To grant unlimited space, set this value to 0.
If you are having issues uploading larger files, see this article for common ways to troubleshoot it.
Control exactly which types of files can be uploaded to your BeDesk instance for security and management.
Allowed Extensions: Enter a comma-separated list of file extensions that you want to permit (e.g., jpg, png, pdf, zip). If you leave this field empty, all file types will be allowed, subject to any blocked extensions.
Blocked Extensions: Specify any file extensions that you want to explicitly forbid, even if the "Allowed Extensions" field is empty.
Note that files uploaded by users are not executable, so you don't need to include any file types in Blocked Extensions list for security purposes.