Files Management#
Files Manager gives you full control to upload protected software binaries (loaders, DLLs, updates), set access permissions, and manage secure file distribution.
What is Files Manager?#
The Files Manager is a secure file distribution system for delivering application assets and executables to authenticated client software.
Uploaded files are application-specific; files for one application cannot be accessed by clients of another.Client applications download protected files by calling the download endpoint with a fileid and sessionid. Files are streamed with SHA256 checksum verification.
Uploading a File (uploadModal)#
To upload a new file, click the Upload File button and provide the following details:| Parameter Field | Description | Example |
|---|
| Direct File URL | Direct HTTPS download link for the protected binary. | https://cdn.domain.com/loader.exe |
| File Note | Internal descriptive note for identification. | Main Loader Build v1.2 |
| Authenticated Access | Toggle to require authenticated access (True / False). | True (Only logged-in users) |
Access Permission Modes#
Authenticated Access = True: Clients must present a valid, active sessionid to download the file.
Authenticated Access = False: The file is publicly accessible for download.
💡 Note: When Authenticated Access is enabled only authenticated users can download the file; public requests are rejected.
File Operations & Management#
Edit File (editModal): Update the download URL or file note text.
Download File: Verify or test the configured file URL from the dashboard.
Delete Single File (delete): Remove an individual file entry from the application.
Delete All Files (delete_all): Clear all files for the application in one action (confirmation required via bulkConfirmModal).
Security Best Practices#
Enable Authenticated Access for sensitive executables.
Host file URLs on trusted HTTPS storage providers.
Upload updated files after a new software release and remove old builds.
Only enable public downloads for files that do not require authentication.
💡 Developer Tips#
Use versioned build names instead of stable filenames (example: loader_v1.2.exe).
Use the File Note field for release notes so builds are easy to identify from the dashboard.
If the client SDK supports file downloads, implement proper error handling for download failures.
Modified at 2026-07-30 15:41:10
