Feature catalogue

Switching features on and off

Your organisation licenses a set of features. The Features screen shows what you hold and lets you switch each one on or off. Switching a feature off removes it from the screen everywhere it appears.

Off means invisible. You do not have to hide the screens yourself, and nobody can reach a switched-off feature by typing its address.

What “off” removes

When a feature is off, everyone in your organisation stops seeing all of it:

Surface What disappears
Navigation The icon in the left rail, and the entries behind it
Pages The page itself, even when opened from a saved link
Settings The feature’s settings pages, and its tile when nothing else is left on it
Record tabs The tabs on an account, counterparty, operating entity or external account
Table columns Columns that only make sense with the feature — in the table and in its exports
Views The named views above a list, such as the ones for a specific product
Actions The feature’s entries in an action menu

An entry that is not part of any feature is always shown. Switching everything off still leaves you a working system.

If your configuration requires a record, the place to capture it stays visible. An account type that needs a credit limit before activation keeps the credit limit tab, even while that feature is off. The feature hides its optional screens; it never hides the field that satisfies a requirement you have configured.

A feature switch is not a behaviour switch

The switch controls what people see, sell, and newly capture. Your configuration — account types, rails, compliance rules — controls what the running system does.

Switching a feature off does not stop the work your configuration drives. Arrears are still tracked, statements still produced, postings still made. That history is kept, so the day you switch the feature on, its screens open with the record complete.

If you want a behaviour to stop, change the configuration that drives it — remove the rail, the statement cycle, or the rule — rather than switching the feature off.

Licensed, and switched on, are two different things

Two separate answers decide what you see.

You can hold a licence and keep the feature off. Its help articles and release notes stay readable while it is off, so you can read up on a feature before deciding to switch it on.

Every feature can be switched off. There is no feature you are obliged to keep.

Features that contain other features

Some features sit inside a larger one. Multi-currency contains exchange rates and foreign-exchange revaluation, for example.

Switching off the larger feature switches off everything inside it. Switching off one of the smaller ones leaves the rest alone.

flowchart TD
    A["Multi-currency: ON"] --> B["Exchange rates: ON"]
    A --> C["FX revaluation: OFF"]
    B --> D["Rates screens visible"]
    C --> E["Revaluation screens hidden"]

A feature can also depend on another one. If something it depends on is off, it is off too, even where its own switch says on.

Switching a feature off does not delete anything

Records made while a feature was on stay exactly as they are. Balances do not move and history is not rewritten.

Switching the feature back on brings its screens back with the records still there.

Some features warn you when you switch them off, because work is in flight — an unexpired notice, or an open settlement quote. Read the warning before confirming; it tells you how many records are affected.

If your configuration still requires the feature, the warning also names what requires it — the account types, compliance rules, or rails involved. You can then change that configuration first, or confirm and switch the feature off anyway.

What your organisation configures