Platform data and staff

Reference data

These lists are shared by every tenant on the platform. A merchant picking a country or a bank is choosing from what you maintain here.

Screen	What it holds
Countries	Name, dialling code, ISO codes, currency, decimal places, operating status
Regions	Administrative regions, maintained per country — pick the country first
Banks	Banking institutions per country
Regulators	Industry regulatory bodies per country. Tenant company forms pick from this list

Each has a New button, a search, and a delete with a proper confirmation. Nothing here is destructive beyond removing an option merchants may already have selected.

Payment gateways

Platform → Payment gateways holds the platform-default gateway credentials — the ones used by any tenant that has not configured their own — and lets you see tenant overrides.

The form takes the Provider, Purpose, Display name, Priority, the Provider keys (JSON) and a Webhook secret.

Marketplace

Marketplace categories is the host-owned taxonomy every seller files listings under. Categories are retired rather than deleted.

Marketplace vendors lists every store. Changing a store’s status opens a confirmation that spells out the effect — suspending, for instance: “The store page and its listings leave the public marketplace. The seller cannot publish until you reinstate it. Their own storefront is untouched.” Suspending and closing both require a typed reason, shown to the seller.

Marketplace listings moderates individual listings with three actions:

Reinstate — back to published, visible immediately.
Send back — returns it to draft so the seller can fix and re-publish without you.
Suspend — removed, and only this console can lift it.

Storefronts and themes

Tenant storefronts is deliberately read-only — “provisioning, status and theme all belong to the merchant.” There are no row actions.

Storefront themes is the catalogue merchants choose from. Each theme has a key, name, layout, description, preview image, status, sort order, a Minimum tier and JSON blocks for its colours and fonts.

Your operator accounts

Settings → Back-office users and Settings → Roles manage your own staff — the people who can sign into this console. Nothing here affects any tenant’s users.

Adding an operator

Go to Settings → Back-office users and create a user.
Fill in Username, Email, First name, Surname and Phone number.
Set a Password — required when creating. On an edit, “Leave blank to keep the current password.”
Leave Active on. Turning it off blocks sign-in without deleting the account.
Leave Lockout enabled on so repeated failed sign-ins lock the account.
Tick Must change password at next sign-in if you set a temporary one.
Pick the Roles.
Save.

The Permissions action on a row adjusts one person directly — role-inherited entries are locked, and only direct grants and denials can be toggled.

Deleting warns “The account can no longer sign in to the back office. This cannot be undone.”

Roles

A role has a Name and three switches: Default role (given automatically to every new back-office user), System role (seeded by the platform; renaming or deleting may be refused) and Public role.

Deleting one warns “Operators holding this role lose everything it granted them.”

Platform settings

Settings → Configuration holds the global defaults every tenant inherits unless they override them at a narrower scope. Settings are grouped by area, with a search and an indicator showing which have been overridden.

Branding

Settings → Branding shows how the console is white-labelled: the logos, the identity details, and a set of theme controls.

Two non-functional controls

The search box in the top bar does nothing — no handler is wired to it. The notifications bell does nothing either, and displays an unread dot permanently.

The version in the sidebar footer is hard-coded and does not track releases.