The control room: system settings, email branding, menus and permissions, intervention types, required documents, letter templates and grant windows — behaviour changed without code.
demo.admin
🗺Configured once, applied everywhere
How the module fits together end to end. Colours mark who acts: navy = staff/admin, cyan = external user, green = organisation, orange = the system.
Administrator
System Settingskeys & values
→
Email brandinglogo, colours, tagline
→
Menus & functions
→
Templates & windows
↓
System
Applies everywhereno code changes
→
Emails, menus, grants, lettersreflect the configuration
🧭1. Email Branding Process
Dress every email the system sends — once.
1
Open Email Branding./Configuration/EmailBranding/EmailBrandingOverview — name, logo, colours, tagline, footer.
↓
2
Judge it on the live preview. The preview renders a real message in the brand — readable or not is decided here, not in an inbox.
↓
3
Save. It applies to the next email sent — no template editing.
↓
4
Every template wears it. The message templates carry only their words; the shell around all of them is this one configuration.
🧭2. Menu & Function Publishing Process
A new screen reaches a user’s sidebar through four gates.
1
Register the function. A data code under its module — the unit access is granted against.
↓
2
Add the menu item./Configuration/Menu/MenuLevelOverview — parented into the RENDERED tree; an item attached to an orphaned parent is silently dropped by the sidebar.
↓
3
Grant it./Configuration/GroupFunctions/GroupFunctionsOverview — at user-type level AND job-title level; a titled user is evaluated against the exact title.
↓
4
Wait out the cache. Menus are cached for hours — allow time or recycle before declaring it broken.
⚙️System-wide settings
System Settings /Configuration/SystemSettings/SystemSettingsOverview
The key-value register behind system behaviour: email templates, feature flags, integration keys.
Search the setting by name.
Edit its value — it applies on the next read (some values are cached briefly).
⚠️ Treat values that look like keys or passwords with care; changes take effect system-wide.
What outgoing email looks like: the name it goes out under, logo, primary/accent/second-accent colours, tagline, footer and website. A live preview shows exactly how a message will arrive.
Set the name and tagline.
Upload a logo (about 280×90 works best; PNG/JPG).
Pick the colours or type hex values.
Save — it applies to the next email sent.
💡 The current install ships Nexus ERP branding: navy #0F2F5F, cyan #22D3EE, flame #EA580C, tagline “Enterprise Resource Planning”.
🔑Menus, functions and access
Menu Levels /Configuration/Menu/MenuLevelOverview
The sidebar itself: groups and items, their icons, order and target URLs.
Add an item under the correct parent group.
Give it the data code matching its function so access checks work.
⚠️ An item attached to a parent outside the rendered tree silently disappears — anchor to the group that actually shows.
Functions & Group Functions /Configuration/GroupFunctions/GroupFunctionsOverview
Functions are the permission atoms; Group Functions grant them per user type and title.
🛠️Programme configuration
Learning Unit Types /Configuration/LearningUnitType/LearningUnitTypeOverview
The intervention types (learnership, skills programme, bursary…) the QA and DG modules run on.