School administration
Staff, roles, permissions, campus scope, identity and branding — what the offline foundation already does, and what waits for connected staging.
A school administrator manages staff, roles, permissions, campus scope, identity and branding for their own school and nothing beyond it. Platform administration is a separate plane. Below, what the offline foundation already does is kept apart from what waits for an accepted connected environment.
Already in the offline foundation
Implemented and validated on synthetic fixtures.
- OfflineSchool registration and activation
A registration creates the school tenant, its first campus, its academic year and its entitlement snapshot in one step.
- OfflineStaff invitations with a role and a scope
An administrator invites a colleague to a role at school, campus, department or section level — never outside their own school.
- OfflinePermissions checked on the server
Every page and every action re-checks the role, the permission and the scope. Hiding a menu is a courtesy, not a control.
- OfflineAudit history
Administrative changes are recorded with who, what and when, in the same transaction as the change.
- OfflineSchool identity and branding
Display name, legal name, timezone, contact details, colours and the fallback mark, with contrast checked before a colour is accepted.
- OfflineLogo rules
File type, size and dimensions are validated before a logo can be accepted.
- OfflineGrading policy by effective date
A school defines its own letter, percentage, standards-based or hybrid policy with an effective date; nothing is hardcoded.
Awaiting connected staging
Designed or built as contracts; not usable until connected staging is accepted.
- AwaitingReal accounts and sign-in
Identity through the connected provider, with multi-factor enrolment for privileged roles.
- AwaitingInvitations delivered by email
An invitation becomes an email only through a governed delivery adapter, after the notification boundary is accepted.
- AwaitingPersisted school records
The reviewed database schema with row-level security, applied and verified in the connected staging environment.
- AwaitingPlatform administration
The separate platform control plane that activates modules and manages school lifecycle; its first bootstrap is under review.
Noble Leadership AcademyMain Campus · West Campus · 2026–2027 · Quarter 1Demonstration configurationHow a school makes IvyDesk its own
Per the documented branding, domain and app roadmap.
- OfflineLogo, colours and campus identity
A school uploads its own logo and chooses its colours; IvyDesk checks the file and the contrast before anything is shown to staff. The offline foundation already validates both.
- PlannedSchool subdomain
A workspace address of the form school-handle.ivydesk.app, resolved to exactly one school and one environment on the server. Planned after connected staging is accepted.
Roadmap. Custom domains and branded packages come after connected staging is accepted. - PlannedPremium branded experience and Signature App
A verified school-owned domain, branded sign-in and reports, and later a school-named mobile app built from the shared IvyDesk app factory. Planned; always with visible IvyDesk attribution.
Roadmap. Custom domains and branded packages come after connected staging is accepted.