← All module guides
Nexus ERP · User Guide

Platform Administration

The glue around every module: webhooks that tell other systems when things happen, reports that email themselves on a schedule, module extensions you can switch on and off, the topbar AI assistant, the language switcher, and the mobile push-device registry.

demo.admin

🔗Webhooks

Subscriptions & deliveries /Administration/Webhooks/Index

A webhook tells another system the moment something happens here — a case created, an invoice issued — by POSTing a signed JSON message to a URL you give it.

  1. Open Administration → Webhooks.
  2. Add a subscription: pick the event and paste the receiving system's target URL, then save.
  3. The signing secret is generated on save and shown once in the banner — copy it to the receiving system right away. It signs every delivery (X-CMIS-Signature) so the receiver can prove the message came from here.
  4. Click Test to send a ping and confirm the receiver answers.
  5. Watch the delivery log on the same page: every POST with its response code, so a failing receiver is visible at a glance. Failed deliveries can be pushed again with Process pending.
⚠️ Treat the secret like a password. If it leaks, delete the subscription and create it again for a fresh secret.
Webhooks with delivery log

📤Scheduled reports

Reports that send themselves /Administration/ScheduledReports/Index

  1. Open Administration → Scheduled Reports.
  2. Add a schedule: choose the report, the recipients, how often it should go, and the format the attachment should arrive in.
  3. Save. From now on it runs itself on the schedule and emails the result.
  4. Click Run now to fire one off immediately — the quickest way to test the whole chain, email delivery included.
  5. Delete a schedule when nobody reads it any more.
Schedule the Monday-morning pack to run before people arrive — it is waiting in their inbox instead of someone exporting it by hand.
Scheduled reports

🧩Extensions

Switch modules on and off /Administration/Extensions/Index

Nexus ships many modules; not every organisation uses them all. Extensions is where a module is activated for this deployment.

  1. Open Administration → Extensions. Each row is a module with its activation state.
  2. Toggle a module on to activate it (capture the licence reference if you have one) — its menus and screens appear for users whose roles grant them.
  3. Toggle it off to retire it — the module disappears from menus; its data stays put.
⚠️ Switching a module off hides it for everyone. Check with the teams using it before you flip the switch.
Extensions

🤖The AI assistant in the topbar

Ask it about your own data

The assistant bubble in the topbar answers plain-language questions — and it only ever sees the data the signed-in user is allowed to see.

  1. Click the assistant icon in the topbar and type a question.
  2. It can answer things like: my service desk cases, the open case queue (and SLA breaches), my classes and enrolments, classes starting soon, levy income summary, outstanding debtor balances, WSP submission status and enrolment statistics.
  3. Ask something it does not know and it replies with the list of things it can do — no guessing, no made-up numbers.
The assistant is scoped to the person asking: a learner asking “my cases” sees their own cases, never someone else's.

🌐Language switcher

Per-user language

  1. Any user clicks the language dropdown in the topbar and picks their language.
  2. The choice is remembered (a cookie) and the interface labels switch immediately — it is per user, not system-wide.

📱Push-device registry

How mobile notifications find a phone

There is nothing to click here day to day — but it helps to know how it works when someone asks why their phone is quiet.

  1. When a user signs in on the mobile app, the app registers the phone's push token against their account — that registry is how the server knows which devices belong to whom.
  2. When something notifies them (a case update, an approval), the server sends a push to every registered device of theirs.
  3. Signing out, reinstalling or switching phones re-registers automatically on the next sign-in; stale devices simply stop being valid.
User not getting pushes? Have them sign out and back in on the app (re-registers the device) and check the phone's notification permission for the app.

❓FAQ & troubleshooting

I lost the webhook secret.

It is shown once, at creation. Delete the subscription and add it again — a new secret is generated and shown in the banner.

Deliveries to my webhook keep failing.

Read the delivery log's response codes. A 404 means the target URL is wrong; a 401/403 usually means the receiver rejects the signature — check it verifies with the right secret.

A scheduled report never arrives.

Use Run now to test. If that email arrives, the schedule's timing or recipients are wrong; if it does not, the mail settings or address are the problem.

A module is missing from someone's menu.

Two gates: the module must be activated under Extensions, and the user's role must grant it. Check Extensions first, then the role's menu grants.