Download the latest module release
Open the module page and use its Latest release button. Download the release ZIP rather than the repository source-code archive.
Browse module releasesEvery AdamCoffeeOverflow community module follows the same clean installation path: download the release, extract it, upload the full module folder, then enable it inside FreeScout.
The module folder always belongs inside FreeScout’s /Modules directory. How you reach that directory depends on your host, container, or server setup.
Open the module page and use its Latest release button. Download the release ZIP rather than the repository source-code archive.
Browse module releasesAfter extracting the download, you should have one complete module folder.
SmartSearchUI/
├── Controllers/
├── Providers/
├── Resources/
├── Routes/
├── composer.json
└── module.jsonUpload the entire module folder—not only the files inside it.
Connect to your server, open your FreeScout installation, and navigate to:
/Modules/Upload the extracted folder so the final path looks like:
/Modules/SmartSearchUIDo not upload community modules into /public/modules, and do not modify FreeScout core files.
Sign in as an administrator and open:
The module should appear automatically after the folder has been uploaded correctly.
Some modules work immediately after activation. Others add settings under the module page, mailbox settings, or user permissions.
Open the module, confirm its settings, and test the affected workflow before using it in production.
Any secure SFTP client can do the job. These are practical, widely used options.
A modern Windows SFTP client that has been reliable for day-to-day FreeScout file work.
A mature Windows client with strong synchronization and file-management features.
A common cross-platform client that supports SFTP and is familiar to many users.
A clean file-transfer client that works especially well for macOS users.
These are suggestions, not requirements or endorsements. Download software only from its official publisher or trusted app-store listing.
You normally need four pieces of information:
Once connected, locate the root of your FreeScout installation and open the /Modules directory.
A module installation is simple, but it should still be treated like a software change.
Keep a recent database backup and a copy of your FreeScout files before installing or updating a module.
Review the module page for its current FreeScout version, licence, release notes, and any specific requirements.
Confirm the affected pages, permissions, mailbox behavior, and mobile layout before broader use.
Retain the previous module version so you can restore it if the new release does not behave as expected.
AdamCoffeeOverflow modules are designed to remain contained inside their own module folder and avoid direct core-file modifications.
Normally, yes. Back up first, review the release notes, replace the module files, and follow any module-specific migration instructions.
Settings normally remain during a standard update, but every release should still be reviewed for migration or configuration notes.
Yes. Disable it inside FreeScout first, then follow the module’s removal or rollback instructions before deleting its folder.
The destination is the same: the FreeScout /Modules directory. The access method may differ depending on whether your host provides SFTP, a file manager, SSH, or container access.
This guide covers AdamCoffeeOverflow community modules. Use the official FreeScout resources below for platform installation, supported environments, and the distinction between official and community modules.
Review the current application requirements, source structure, releases, and security information.
Platform setup FreeScout installation guideUse this when installing or maintaining FreeScout itself—not for the module upload steps above.
Official catalogue Official FreeScout modulesOfficial modules are distributed and managed by the FreeScout team through their own module workflow.
Community catalogue Community modulesCommunity modules are independent projects. Always follow the release notes and installation instructions provided by their maintainer.
AdamCoffeeOverflow modules are independent community modules. They are not official FreeScout modules and are not endorsed or supported by the FreeScout team.
AdamCoffeeOverflow modules are built to extend FreeScout while keeping the underlying installation maintainable. Each release remains independently versioned, reviewable, and removable.