Two controls, not one
People trip over this once and then never again, so it is worth being explicit. Entitlement is what your organisation has bought or been granted — a list of module keys on the organisation. Module access is which of those a specific person may open. Access can only ever remove; a row granting somebody a module the organisation does not have grants nothing at all.
| Entitlement | Module access | |
|---|---|---|
| Scope | The whole organisation | One person |
| Set in | Settings → Modules | Admin → Module access |
| Direction | Grants | Restricts only |
| Absent means | Module is not available at all | Inherit the organisation |
| Affects billing | Yes | No |
Turn a module on
At app.erp.io/settings/org/modules. Every module in the suite is listed with a one-line description.
The rail updates immediately — for everyone, not just you.
The first person from your organisation to enter a module causes it to mirror your organisation into its own storage and create their user there as an administrator. Nothing happens until somebody walks through the door.
If only finance should see Accounting, go to Admin → Module access and remove it from everybody else.
Modules
6 of 12 enabled — included in your plan
Turning one off
Disabling a module removes it from the rail and refuses the hand-off token, so nobody in the organisation can enter it. It does not delete anything. The module keeps its mirror of your organisation and every record in it, and switching the module back on returns you to exactly where you were.
What it does affect is anything another module was reading across. Turning off CRM while Accounting is putting CRM company names on invoices leaves those invoices intact — the name was copied at the time, not looked up on render — but new invoices will not offer the picker.
Accounting is stored as finance, Phony as sdr, Chat as messaging, Projects as pm. These are historical and deliberately not renamed: the key is the audience claim on every hand-off token and the value in every entitlement row, so renaming it would sign every existing customer out of a module they are entitled to. You will see the old keys in API responses and in the audit log. The product name and the key both resolve on the way in, so /sign-up/accounting and /sign-up/finance both work.
What this does not do
The trial grants everything. There is no way to trial one module for longer than the others.
Disabling a module does not reduce a bill mid-term. Plans price users against modules at the plan level.
Pey is a separate product with its own account, not a module you switch on here. See Pey.
Questions
If I turn a module off and on again, is my data still there?
Yes. The module keeps everything; entitlement only controls the door.
Can I hide a module from everyone except me?
Yes — enable it for the organisation, then remove it from everyone else in Admin → Module access.
Why does a module I enabled show nothing?
Most likely nobody has entered it yet, so it has not mirrored your organisation. Open it once.
Related
Per-person control over which erp.io modules somebody can open. Restrict-only by design, enforced at the hand-off, and invisible until you use it.
ModulesThe twelve applications available on app.erp.io — what each one is for, what is built, and what is named in the product but not finished.