Issue
The Lightspeed Parent Portal is a district-provided service used directly by parents and guardians, but the current presentation provides limited ability for the district to apply its own organizational branding consistently across the experience.
Because Parent Portal instances are district-specific and presented through their own tenant/domain context, it appears reasonable for branding to be configurable at the district level and then inherited across the family-facing experience.
WCPSS would like Lightspeed to establish a district branding standard for Parent Portal rather than limiting customization to a single landing page.
The objective is to ensure that parents immediately recognize the service as an official WCPSS resource while still clearly identifying Lightspeed as the technology provider.
Requested Enhancement
Provide centralized tenant-level branding controls that apply across Parent Portal and associated family-facing communications.
At minimum, district branding should be supported in:
Parent Portal landing page;
authenticated Parent Portal experience;
Parent Portal headers and navigation;
automated parent emails;
scheduled or generated reports;
parent-facing notifications;
downloadable reports or PDFs;
support/instructional messaging generated by Parent Portal;
other family-facing Parent Portal communications.
Preferred Branding Hierarchy
The primary visual identity should be the district.
For example:
WCPSS Logo
Wake County Public School System
Parent Portal
with secondary attribution such as:
Powered by Lightspeed
The relationship communicated to families should be:
WCPSS provides the service — Lightspeed powers the platform.
Lightspeed attribution should remain visible and appropriate, but it should not visually compete with the organization delivering the service to the family.
Centralized Branding Configuration
District administrators should be able to define branding once and have it applied consistently throughout the Parent Portal ecosystem.
Suggested settings include:
Organization Identity
District Name
District Logo
Parent Portal Display Name
Optional district tagline
Brand Appearance
Primary color
Secondary/accent color
Header color
Link/button color
Logo alignment
Logo sizing
Light/dark logo variant where supported
Messaging
Welcome text
Introductory instructions
Support/contact information
District help URL
Optional footer text
Terms or district-specific informational messaging where appropriate
Vendor Attribution
A standard secondary attribution such as:
Powered by Lightspeed
should remain available throughout the experience.
Parent Portal Landing Page
The landing page should allow the district logo and identity to serve as the primary visual header.
Preferred hierarchy:
District Logo
District Name
Parent Portal content / sign-in experience
Powered by Lightspeed
This would make the portal immediately recognizable as an official district service.
Authenticated Parent Portal
District branding should persist after authentication.
The experience should not transition from a district-branded landing page into a substantially different vendor-branded application.
Applicable elements could include:
header;
navigation;
logo;
accent colors;
support information;
footer;
district name.
The entire parent experience should feel like one consistent service.
Parent Emails and Notifications
Emails generated by Parent Portal should also use district branding.
Where practical, parent communications should support:
district logo;
district name;
district brand colors;
district support/contact information;
district-specific footer;
secondary Powered by Lightspeed attribution.
For example, a weekly Parent Portal email should visually communicate that it is an official WCPSS communication rather than appearing primarily as an unrelated vendor email.
This is important for:
parent trust;
recognition;
adoption;
phishing awareness;
consistency with district communications.
Reports and Downloadable Content
Reports generated for parents should inherit the same branding standard.
Applicable outputs could include:
activity reports;
scheduled reports;
downloadable PDFs;
summaries;
notifications containing report content.
At minimum, generated reports should be capable of displaying:
district logo;
district name;
report title;
district colors or approved header treatment;
support/contact information;
Powered by Lightspeed attribution.
Branding Consistency Standard
The preferred design principle is:
Configure district branding once → apply it everywhere Parent Portal communicates with families.
The district should not need to separately recreate branding for:
the portal;
emails;
reports;
notifications;
downloadable content.
The same approved tenant-level branding configuration should be reused wherever practical.
Tenant / Domain Feasibility
Because Parent Portal instances are already associated with individual district tenants and domains, a tenant-scoped branding profile appears to be a reasonable approach.
A potential model would be:
District Tenant
→ Branding Profile
→ Landing Page
→ Authenticated Portal
→ Emails
→ Reports
→ Notifications
This would allow each organization to maintain its own identity without affecting other Lightspeed customers.
The exact implementation is for Lightspeed to determine, but the district-specific nature of the Parent Portal makes centralized tenant branding a practical feature request.
Administrative Controls
Branding configuration should be restricted to appropriately authorized administrators.
Where possible, administrators should also be able to:
preview changes before publishing;
restore default branding;
upload replacement logos;
validate logo dimensions;
preview email presentation;
preview report presentation;
ensure text remains readable against configured colors.
Accessibility
Custom branding should preserve accessibility requirements.
Lightspeed should retain safeguards for:
sufficient color contrast;
readable text;
accessible buttons and links;
appropriate logo scaling;
responsive layouts.
District branding should enhance identity without degrading usability.
Requested Outcome
Establish a Parent Portal branding standard where district identity is centrally configured and consistently applied across all parent-facing experiences.
The desired model is:
WCPSS-branded portal
WCPSS-branded emails
WCPSS-branded reports
WCPSS-branded notifications
with consistent:
Powered by Lightspeed
attribution.
Acceptance Criteria
This request would be considered addressed when:
District administrators can upload and configure a district logo.
The district logo can serve as the primary visual identity on the Parent Portal landing page.
District branding persists throughout the authenticated Parent Portal.
Automated Parent Portal emails can inherit district branding.
Generated reports and downloadable documents can inherit district branding.
Parent-facing notifications can display district identity where supported.
District name, colors, support information, and approved messaging can be centrally configured.
Branding can be managed as a tenant-level configuration rather than recreated separately in each feature.
Lightspeed attribution remains visible in a secondary Powered by Lightspeed position.
Branding configuration preserves accessibility and responsive design standards.
Administrators can preview branding before publishing changes.
Business Value
This enhancement would:
establish immediate parent trust;
make Parent Portal clearly identifiable as an official district service;
improve consistency across all family-facing communications;
reduce confusion between district and vendor ownership;
strengthen parent adoption;
improve phishing awareness by making legitimate communications visually recognizable;
reduce duplicated branding configuration;
allow Lightspeed to remain appropriately credited without dominating the parent-facing experience.
The standard should be simple:
Our families should see our district identity everywhere they interact with the service — with Lightspeed clearly and professionally shown as the platform powering it.