CMS
CMS stands for content management system — this is a website/page builder embedded in the ERP, used to run public-facing tenant websites (landing pages, fundraising pages, and similar). It’s separate from the school, SACCO, or member records elsewhere in the product: nothing here touches student, staff, or member data. A tenant can run more than one of these public sites, each with its own content, media, forms, and menus. There are 6 modules and 30 checkboxes in this group. Modules are listed alphabetically by their internal key, which is also the order they appear on screen.1. CMS Content
The actual pages/articles published on a site — each one has a title, a status (draft or published), a publish date, and the data for whatever content type it belongs to. Only published content is visible to site visitors.2. CMS Content Types
The schema layer behind CMS Content — before you can create a page or article, someone defines what fields it has. This is a headless-CMS-style content model: think of it as defining custom post types (e.g. “Blog Post” with a title, body, and cover image, or a single “Homepage” record).3. CMS Forms
A public-facing form builder. Visitors on a site fill in and submit these forms; submissions are stored (with the visitor’s IP and browser info) and flagged unread until staff review them.4. CMS Media
The file and image library backing a site — used when building pages, forms, and content entries. Each item stores things like alt text, caption, tags, and dimensions alongside the file itself.5. CMS Navigations
The menu builder for a site — header and footer navigation, submenus, and links, defined once and rendered on the public site.6. CMS Sites
The top-level container: a site’s name, URL slug, optional custom domain, API key, and logo. Everything else in this group — content, content types, media, forms, navigations — belongs to one of these.Payments
There are 4 modules and 20 checkboxes in this group.Note — this is school fee management, not general ERP billing. Despite sitting under a generic “Payments” label, these four modules are entirely about school tuition and fees: they were originally seeded under an “Edu360 — Finance & Parent Portal” block alongside the rest of the school product, and their real implementation lives in the school fee/parent-portal feature, not a general-purpose ERP invoicing system. They ended up in this “Payments” group because the role editor sorts modules into groups by matching their key against a pattern list, and any module key starting withModules are listed alphabetically by their internal key, which is also the order they appear on screen.payment,fee-type,fee-categor, orscholarshiplands here — regardless of which product it was originally built for.
1. Fee Categories
The broad grouping a fee belongs to — Tuition, Transport, Uniform, Boarding, Meals, and so on. Used for organizing and reporting on fees, and for scoping which fees a scholarship applies to.2. Fee Types
A specific chargeable item within a category — for example “Tuition — Term 1.” Each fee type has an amount, a currency, a billing frequency (monthly, termly, yearly, or one-time), and can be scoped to a particular academic period, curriculum, or set of classes.3. Payments
The actual record of money changing hands against a student’s invoice — a staff member logging a cash, bank transfer, POS, or cheque payment at the counter, or a parent paying an outstanding balance themselves through the parent portal (by card, mobile money, or similar).Note: Add and View are the checkboxes that actually correspond to something in the product. Edit and Delete exist in the role editor (every module gets the same five checkboxes by default) but have no matching feature to turn on or off.
4. Scholarships
A discount applied to a student’s fees — either a percentage or a fixed amount — with its own validity dates and optional budget/recipient limits. Scholarships are assigned to individual students and applied automatically when their invoices are generated.ERP Settings
There is 1 module and 5 checkboxes in this group.Important — this one permission gates several unrelated settings screens at once. ERP Settings is a shared configuration store used across features that have nothing to do with each other: HR check-in geofencing, chat moderation policy, task productivity scoring, and M&E alert thresholds all read their settings through this single permission. Granting or denying it affects all of those screens at once — it isn’t scoped to just one of them.
1. ERP Settings
Related
- SACCO roles & permissions catalog — the equivalent catalog for the Sacco360 module group, for comparison.