Branding & Customization
Make the platform look like your school — to your staff, your students, your parents, and to anyone who lands on your public pages.
What this module is
Schools spend years building a name, a crest and a set of colours, and then hand their families a portal that belongs to a software company. It is a small thing until you notice how much of it there is: the mark in the corner of every screen, the sign-in page, the ID cards, and the careers site a candidate judges you by.
Branding & Customization replaces all of that with yours. It is not a colour picker bolted onto a settings page — it is a module with its own record, its own permissions and its own operator role, and every surface in the platform reads from it. Change the active theme and the whole estate follows, in the app and on the public pages, without anyone re-styling anything.
It divides into four surfaces. Overview tells you what is set up and what is not. Themes holds up to three saved presets and the accessibility guardrail. Identity holds the assets — logo, per-preset overrides, tagline — and can read your brand colours straight out of your logo. White-label is where the module states, item by item, what your brand has actually replaced of ours.
What you get
Your mark, not ours
The sidebar shows your logo and school name instead of the EaseAcademia one, and the “Powered by EaseAcademia” line comes off your public pages. That removal is the point of the module.
Three looks, one switch
Keep a light/dark pair, or a seasonal variant for a centenary year. Set one active for the school; members can pick any of them from their own theme menu.
Colours pulled from your logo
Upload the crest and the brand kit reads its dominant colours, proposing a primary, secondary and accent with a contrast-safe text colour — instead of you hunting for hex codes in an old style guide.
Accessibility checked as you go
Every text-on-background pair is measured against the WCAG AA 4.5:1 ratio while you edit, so a brand colour that looks smart but reads badly is caught before it ships to a thousand students.
Public pages included
The careers site is served your palette and logo by an endpoint that checks the entitlement server-side — so candidates meet your school, not a vendor.
Set once, read everywhere
Sign-in screens, ID cards and document headers all read the same brand record. There is no second place to update when the colours change.
How Branding & Customization actually works
Everything below is the real application, running live on this page with sample school data — not screenshots. Each screen is the same one your team would use.
School admin
One person usually owns the school’s look — a bursar, a head of communications, or whoever holds the style guide. These four screens are the whole job: see where the brand stands, set the palettes, load the assets, and confirm what has actually been replaced.
Start with where the brand stands
The landing screen is a status report, not a form. It shows the brand as it is currently resolved and, more usefully, what is missing.
Set the palettes
Themes holds up to three presets. Colours are split into the two groups schools actually reason about: brand colours, which come from a style guide, and interface colours, which most schools never touch.
Load the assets
Identity owns everything that is not a colour: the school logo, the per-preset overrides, the tagline, and the brand kit that turns a logo into a palette.
Confirm what has been replaced
The white-label page is deliberately read-only. The behaviour lives in other surfaces reading the same record, so this page reports on them — including what it cannot do.
Teachers & other staff
Staff get no branding screen and nothing to configure. What they get is that the workspace they were already using stops looking like a vendor product.
The same workspace, in the school’s colours
An ordinary staff page arrives in the school palette with the school mark in the sidebar. The only new control is a theme menu that lists the school’s presets alongside plain light and dark.
Students
Students are the largest audience for the school’s brand and the least likely to configure anything. The module reaches them by default rather than by opt-in.
Their school, not a product
An ordinary student screen — here a timetable — themed the moment the school activates a preset. No per-student setting, no first-run prompt.
Parents & guardians
Parents form an impression of a school from its digital surfaces long before they sign in to one. This is where removing the vendor mark earns its keep.
A school-branded parent portal
Parents see the school’s colours and mark rather than ours — on a child’s results here, and on the public pages that lead to the portal.
How it connects to the rest of the platform
The base platform reads one brand record
Sign-in screens, student and staff ID cards, and onboarding all read the same resolved palette and logo. The active preset is mirrored onto the record every save, so nothing needs to know that presets exist.
Access control treats it as its own module
Branding has its own permission namespace and a Brand Manager role, so the person who owns the school’s look does not need broad settings access — and a settings administrator does not silently inherit the brand.
The careers site wears itrequires Human Resource Management
Where recruitment is in use, the public job board is one of the branded surfaces — often the first page a candidate ever sees of the school.
Document templates share the brand kit
Generated documents draw on the same logo and brand assets through the document-template engine.
Common questions
What actually changes for a school that buys this?+
The sidebar mark becomes your logo and school name, your palette applies across every portal by default, your careers site is served your colours, and the “Powered by EaseAcademia” attribution comes off your public pages.
How many themes can we keep?+
Up to three saved presets. One is active for the school and is what everyone gets by default; members can pick any of the others from their own theme menu.
Do we need brand colours to hand?+
No. Upload your logo and the brand kit reads its dominant colours, proposing a primary, secondary and accent plus a contrast-safe text colour. You can adjust anything it proposes.
Can a member turn the school theme off?+
Yes. Choosing plain light or dark in the theme menu opts that person out — an accessibility escape hatch that does not affect anyone else.
What happens if we cancel the module?+
Your presets, logo and colours are kept on your school record. The branded surfaces revert to the platform default and the EaseAcademia attribution returns, and everything comes back as soon as the module is switched on again.
Can we use our own domain?+
Not with this module. A custom domain needs DNS and certificate infrastructure and is treated as a separate premium tier; the white-label page says so plainly rather than implying otherwise.
Run your whole school on one connected platform
Start with the base package, switch on the modules you need, and give every parent, student and staff member a single place to log in.