Going live

The installation responds. Here is what to do before you let anyone in, and what to keep doing afterwards.

Before you open the door

1. The company

Settings → Company holds the legal name, the country, the currency and the time zone.

The last two deserve a minute. They are used to convert and to display, and changing them later does not rewrite history: an accounting entry keeps the rate frozen at its own date. That is deliberate, and it is what makes your books defensible.

An empty currency gives empty prices

If the company has no currency, amounts render blank instead of raising an error. The classic symptom is “the price will not fill in”. Check this setting first.

2. Modules

Settings → Modules lists what is available. Switch on what you need and nothing more: a module that is off clutters neither the menus nor your team’s training.

A module can be switched off again. Its data stays; only the screens disappear.

3. Users and their rights

Create the accounts, then give each one its groups. A group is a set of rights; it decides what a user sees and may change.

Take your time here. Opening a right later is far easier than un-seeing a record somebody should not have seen.

4. Outbound mail

Settings → Mail holds your sending server. Test it before opening: a user who never receives their initial password opens a ticket on day one.

5. Backups

Set them up before the first real record, not after.

A backup without its key is not a backup

Confidential data is encrypted with your installation’s master key. A database restored without that key leaves those fields unreadable.

Keep the key somewhere other than the server being backed up, and test a full restore before you need one. A backup never restored is a hypothesis.

Habits worth keeping

After every upgrade

A new release may bring schema changes. The upgrade procedure shipped with the package applies them; it never erases anything.

Then check the installation reports itself healthy:

curl https://erp.your-domain.com/health/live

Watch three things

What	Why
Your licence expiry	A banner will warn you, but a renewal takes preparation.
Disk space	Attachments and backups grow without asking.
Your backups	Not that they run: that they restore.

What will raise questions first

In order of observed frequency.

An empty list although the data exists. Almost always a question of rights: the account does not see those rows, or not that company. Permissions apply beneath the interface, so an empty list is a correct answer, not a failure.

An email that does not go out. Sending is queued, never done from the screen. If the worker service is not running, the message waits with no visible error.

A user who cannot see a module that is switched on. They are missing the matching group.

An amount shown without a currency. See the company setting above.

Getting help

Write to support@kewos.io with your version number and, if the service will not start, the last lines of its log.