Settings is organized by what a group of settings decides rather than by when you happen to need it. This page is a map: what lives where, and which settings change behavior rather than wording.
General
The identity of the installation: company name and address, the System URL, date and number formats, the default language and currency, and maintenance mode.
Emails, payment gateway callbacks and generated links are all built from it. Changing it without updating the gateway callbacks configured at each provider will silently break payment notifications.
Maintenance mode
Maintenance mode takes the customer-facing side offline while leaving the administration area reachable, so work can continue during an outage window. It does not stop the scheduler.
Tax configuration
Tax rules are evaluated against the customer’s address at the moment an invoice is generated. Decide the tax type, whether prices are shown inclusive or exclusive, and which levels apply to which jurisdictions.
- Set the tax type and inclusive or exclusive display before creating rules; changing it later re-frames every price on the site.
- Add rules from the most specific jurisdiction to the least, so a country-wide fallback does not shadow a regional rate.
- Check an actual generated invoice for a customer in each jurisdiction. Rule tables read correctly far more often than they calculate correctly.
Currencies
The default currency is the one your accounts are kept in; additional currencies carry their own rate and their own prices. Automatic rate updates run from the scheduler, so rates go stale when the automation is not running.
Notifications
Notification rules decide which events reach which people, on which channel. A rule names an event type and a set of events within it, so adding an event to an existing rule is usually right where adding a rule is not.
Notifications tell your team something happened. Email templates are what the customer receives. Editing one has no effect on the other.
Email templates
Every message the product sends is a template: sender, recipients, subject and body, with merge fields listed beside the editor. A template is addressed in code by name, so renaming one stops the message being sent rather than sending it under a new title.
The product looks templates up by name. A renamed template is a message that silently never arrives.
Custom fields and merge fields
Custom fields extend clients, products and tickets with data of your own. Merge fields expose data to email templates and documents. A custom field added for a report is cheap; one added to every order form is a question every customer must answer.
Order statuses
The order status list is editable, but the four defaults — Pending, Active, Fraud and Canceled — cannot be deleted or renamed, because the product decides behavior from them. A status you add is a label; the four defaults are wiring.
Client groups
Client groups carry a discount and a color, and group members can be filtered and priced together. The color is used wherever the group is shown, so choose values that stay legible in both light and dark themes.
Automation settings
What the daily automation is allowed to do: which tasks run, when the day starts, and the thresholds for suspension, termination and reminders. These settings are inert if the scheduler itself is not running — see Automation and scheduler.
Support settings
Ticket departments, statuses, escalations, spam handling and the ticket mask format. The mask decides what a ticket reference looks like to the customer and appears in every support email, so settle it before the first ticket rather than after the thousandth.
Theme and appearance
The administration area ships one theme. Theme settings control the light and dark modes, the defined-regions layout switch, and the branding shown in the shell. Client-facing appearance is the Draisap theme and the order form, configured separately.