Operations

Data purge

Operations → Data purge — “Estimate and permanently delete a tenant’s business data.”

This cannot be undone. Read this section before opening the screen.

There is no undo, no soft-delete, no export-first and no restore. The only recovery is a database restore from backup.

It is also all-or-nothing: the whole purge runs in one transaction, so it either completes or deletes nothing. A half-purged workspace is not possible.

What it deletes, and what it never touches

The purge finds every table belonging to that tenant and empties it — except:

Never deleted, whatever you choose:

• Users, roles, permissions and sessions. Staff accounts survive a purge.
• Audit log, outbox and other internal records.
• The tenant itself. The workspace continues to exist.

Two modes:

• Transactional only (the default) deletes the trading history — sales, purchases, stock movements, invoices — and keeps the setup behind it: products, variants, categories, brands, units, attributes, customers and suppliers, chart of accounts, tax groups and rates, storage locations, and the whole of the organisation and settings data.
• Include master data deletes those as well. It leaves an empty shell with its staff accounts intact.

How to run one

1. Go to Operations → Data purge.
2. Choose the Tenant.
3. Choose the Scope — Entire tenant, Company or Location — and the company or location if you narrowed it.
4. Choose the Mode.
5. Click Estimate. This is “A safe, read-only dry run — nothing is deleted.”
6. Read the Rows to be deleted table carefully. That is exactly what will go.
7. Type the tenant’s name into Type the tenant name. It must match exactly, and it is case-sensitive.
8. Click Permanently purge.

The purge button does not exist until you have run an estimate, and changing any option clears both the estimate and what you typed — deliberately, so the thing you confirm is the thing you were shown.

The typed name is also re-checked on the server, so the confirmation cannot be bypassed from the browser.

If the tenant shows as a long hex identifier, do not try to purge it

The tenant dropdown on this screen is built from a different source to every other picker in the console, and when it cannot resolve a name it falls back to the raw identifier — then asks you to type that as the confirmation.

The server compares what you type against the real tenant name, so it will never match and the purge will be refused. Get the correct name from Overview → Tenants first.

A tenant with no subscription does not appear in this dropdown at all.

A company-scoped purge that fails is usually the design protecting you

Some records cannot be attributed to a single company. Rather than guess, the purge refuses and rolls the whole run back. That is a safeguard, not a fault.

Purge history below records every run — started, tenant, scope, mode, status, rows deleted and duration. It keeps the last 50 with no pager and no filter.

Background jobs

Operations → Jobs — “Durable job queue — monitor, trigger, retry and cancel scheduled work.” Tiles for Jobs shown, Running, Retryable and Discarded, filter tabs per state, and columns Kind, State, Queue, Attempt, Scheduled and Finalized.

Click a job to inspect it: its Arguments, its Error history attempt by attempt, and its Metadata. From there you can Retry (“Re-run this job now?”) or Cancel (“Cancelling stops the job before it runs. This cannot be undone.”).

Operations → Job kinds is the catalogue: every job the scheduler knows about, grouped by area, with its schedule and description, and a Run now on each row.

Trigger jobs from the Job kinds page

The Trigger job button on the jobs list takes a free-text Job kind with no autocomplete, so a typo just produces an error. The Job kinds page has a Run now button per row and cannot be mistyped.

The jobs list fetches 500 jobs with no pager, and its queue filter can only be set by editing the address bar.

Support tickets

Operations → Support tickets — tenant requests across the platform, with tabs for Active, Unassigned, SLA breached and Assigned to me, then per-status tabs. Rows sort breached-first, then by priority.

Open a ticket to change its Priority and Status, Assign to me, Assign to…, or Resolve with an optional closing message. The composer has a Public reply tab and an Internal note tab, and can set the status as you send.

Tickets can only be raised by tenants — there is no new-ticket button.

Priority and Status save the moment you change them

Both dropdowns write immediately, with no confirmation and no undo. A mis-click on a customer’s ticket is live at once.

Assigning to someone else needs their identifier

Assign to… asks for an “Operator user id” — a raw identifier with no picker, despite Settings → Back-office users listing every operator. Leave it blank to assign the ticket to yourself.

Report contracts

Operations → Report contracts — scheduled reports you deliver to a tenant at your own cost rather than theirs.

1. Click New contract, choose the Tenant and Company, give it a Name, and click Create contract. It is created inactive.
2. On the detail page, add Report lines (the report, its frequency and channel) and Recipients.
3. Set the Schedule — send time, timezone, weekly day, monthly day — and Save changes.
4. Tick Active.

“Run now” sends real reports immediately, with no confirmation

One click delivers every active line to every real recipient, whatever their cadence. There is no dialog and no dry run.

It does not advance the schedule, so the regular send still happens as well.

Service engagements

Operations → Service engagements tracks paid onboarding, setup, training and support work. Create one against a tenant with a type, unit, quantity, package name and contact details, then drive it through Schedule, Start, Complete or Cancel.

Catalog seed

Operations → Catalog seed fills a tenant company with realistic sample products so inventory flows have something to work with. The screen labels itself a Developer tool.

Choose the Tenant and Company, tick the Verticals and Product types, choose Locations, and set the Level. Preview is a safe dry run; Seed catalog writes.

It is additive and repeatable — an existing product code is skipped rather than overwritten, so running it twice is harmless.

Seed catalog has no confirmation, and posts real stock by default

One click writes to whichever tenant is selected, and “Post opening stock at the selected locations” is ticked by default — creating real inventory movements in a live customer’s books, not just catalogue rows.

There is no un-seed. The only way to remove seeded data is a data purge, which is a far blunter instrument.

Use this on demo and sandbox workspaces. If you must run it against a live tenant, untick the opening-stock box and use Preview first.

This screen is also the one part of the console with no translations at all — it is English only.

Related

• The host console
• Dunning and collections
• Tenants