Wrong logo
Old crest still on the parent app.
Your campus brand — on every portal login
Theme & Branding lets trusts apply logos, color tokens, and login artwork so parents and staff recognize the institution, not a generic ERP shell.
Logo
& color tokens
Per-campus
brand packs
Preview
before publish
The problem
Why generic ERP skins confuse parents
When five schools in a trust share one blue login, parents are unsure they are in the right portal.
Brand clash
Trust blue overrides school identity.
No preview
IT publishes ugly themes live.
Inconsistent
Web and mobile look different.
Capabilities
What this module actually does
Operational depth your team will use every cycle — not a shallow feature list.
Brand kits
Logo, favicon, primary/secondary colors.
Login artwork
Campaign or campus photography.
Portal scopes
Parent, teacher, student, admin shells.
Campus packs
Different brands per branch.
Preview mode
Stakeholder sign-off before go-live.
Accessibility checks
Contrast guidance for text.
Seasonal skins
Sports day or annual day themes.
Rollback
Revert to last approved kit.
Operating loop
How it works end to end
A clear path your staff and parents can follow without training manuals.
-
01
Upload
Add logo and color tokens.
-
02
Preview
Review portals as parent/teacher.
-
03
Approve
Communications signs off.
-
04
Publish
Push to web/mobile shells.
Who uses it
Role-aware access for every stakeholder
The right people see the right slice of the pipeline.
Communications
Owns kits and artwork.
IT Admin
Applies themes safely.
Campus head
Confirms local identity.
Parent
Sees branded portals.
Connected stack
Works with the modules you already need
Each module is an edge in the campus operating graph — not a silo.
Outcomes
What changes after go-live
Measurable ops wins institutions report once this module runs inside ScholarERP.
Recognizable
campus identity
Safer
publish via preview
Consistent
web + app look
“Parents stopped asking “is this the right app?” after we applied school-specific login art.”
FAQ
Questions teams ask before buying
Straight answers for setup, integrations, and day-two operations.
Can each campus have its own theme?
Yes. Brand packs can be scoped per campus while the trust keeps a default.
Does theming change module logic?
No — only presentation tokens and assets.
Can we match our public website fonts?
Within supported font/token sets; custom webfonts depend on deployment policy.
Is dark mode included?
Where portal shells support it, theme tokens can define dark variants.
Preview a branded parent login
Upload a logo and colors, then flip between campus packs.