Account hygiene
- Use unique administrator credentials.
- Disable or remove accounts that are no longer needed.
- Review access after role changes.
- Do not share one administrator password among a team.
Administration & Customization
Configure Clistor for your organization.
Keep user access, visible branding, operational settings, scheduled work, backups, and security under deliberate administrative control.
User Accounts & Permissions
Use User Accounts to create and manage administrative access. Give each person only the access needed for their role.
Permission hygiene
- Grant access to the minimum required product areas.
- Limit account-management privileges to trusted administrators.
- Review list/template/segment access where applicable.
- Re-check permissions before onboarding a new operator.
Settings
The Settings area is the main place to review environment-specific application values. Configure sending-related values according to the mail infrastructure you actually use.
Do not copy settings blindly between servers. Hostnames, URLs, database access, mail infrastructure, filesystem paths, and license state can be environment-specific.
Branding & visible support links
Clistor 3.1 includes administrator-controlled fields for visible product/footer links. Use them when you need a customer-facing deployment with your own support destinations.
| Setting | Purpose |
|---|---|
| Brand Label | Visible brand text shown in the configured product/footer area. |
| Brand URL | Destination URL associated with the brand label. |
| Updates Label | Visible text for the updates/news destination. |
| Updates URL | URL used for product or organization updates. |
| Support Label | Visible support text. |
| Support URL | Support destination used by the visible link. |
Scheduled tasks & automation
Scheduled sending and automated workflows depend on the server-side scheduler used by your deployment. Configure cron/scheduled tasks according to the Clistor task instructions available inside your installation and the controls provided by your hosting environment.
- Confirm the scheduled task is enabled on the server.
- Confirm it runs under an account with the required access.
- Review server logs if the task runs manually but not on schedule.
- Use the internal Help Center article for scheduled sending and cron troubleshooting.
Production security checklist
Application & network
- Use HTTPS for production access.
- Keep database access private.
- Do not publish configuration files or server paths.
- Protect the hosting control panel and SSH account separately.
Operations
- Back up the database and application files before major changes.
- Keep runtime secrets out of public support screenshots.
- Review user accounts periodically.
- Verify installer/setup access is closed after installation.
Backups & change management
A usable backup needs both the database and the application files relevant to your installation. Take a backup before upgrades, migrations, major settings changes, or infrastructure work.
Restore testing matters. A backup is only useful if you know how to restore it. Test your own backup procedure on a non-production environment where practical.
Help & support
Use the internal Help Center first for task-focused guidance. For product assistance, use the official channels listed below.