The configurator applies pre-built setup packages to an organisation, a ready-made chart of accounts, tax codes, document settings, tuned for a country or a module, so a new org can be stood up from a sensible template rather than assembled from nothing. It is how a Malaysian SME gets a localised starting point in one step.
- What a configurator preset is
- How presets are organised and found
- How a target constraint scopes a preset
- Why presets are file-based
Anatomy of a preset
A preset is a packaged set of configuration with descriptive metadata: a name and description, an example and a notice, and the country and module it targets. The preset directory is searchable and filterable by country and module, so you find the right starting template quickly, the Malaysian retail pack, say, or an accounting-only baseline.
How it behaves
Applying a preset
Applying a preset loads its configuration into the organisation: it seeds the chart of accounts, tax codes, document defaults and whatever else the package carries. This is the fast path to a working setup, a new org can begin from a localised, sensible baseline instead of being built account by account.
Target constraint
A preset can carry a target constraint that limits it to a specific organisation, matched by registered name, permalink or UUID, or it can be globally available. This lets a partner ship a preset intended for one client without it appearing for everyone, while general presets stay open to all.
File-based, by design
Presets are file-based packages, not database records. That is deliberate: because they are shipped as curated files, they stay consistent and versionable, maintained centrally rather than edited ad hoc in each org. You apply them; you do not author them in the database.
Worked example
A new Malaysian retailer's organisation is created, and you apply the “Malaysia / Retail” preset. In one step it gains a localised chart of accounts, SST tax codes and retail-oriented document defaults, ready to trade rather than waiting on a manual build.
Edge cases and good practice
- Apply a preset early, on a fresh org, before manual setup diverges from the template.
- Filter by country and module to find the closest-fitting package.
- Presets are curated files, so request a new one rather than expecting to hand-edit them in the database.
Related
- Reference: Chart of Accounts (what a preset seeds)
- Reference: Tenant Management (partners deploying presets)