Dashboard

Viewing as
View live site β†—
🏫 Super Admin sees everything. Full visibility across the whole district β€” every campus, all content, users, integrations, and audit. Site Admins and below are scoped to their own school; Department Leads only to their department. Switch the β€œViewing as” role up top to see scoping in action.

Dinuba Unified β€” All Campuses

Every school running on the platform
βš™οΈ How this works: Every panel here edits the same content model the public site renders from. Hit Publish and open the live site β€” your change is there. This is the CRM layer: the people running the school manage the front-end without touching code.

Recent activity

Audit trail of content changes

Hero Slides

The rotating banner on the homepage

News & Bulletin

Announcements shown on the homepage

Departments & Academies

18 departments Β· 2 four-year academies

Events

Calendar items on the homepage

Quick Links

Top utility bar + quick-access grid

Staff Directory

Administration & contacts
βš”οΈ The Emperor AI character answers families and students from this content. Because the assistant is grounded in the CMS, every edit you publish also updates what Emperor AI knows β€” no separate training step.

Emperor AI β€” Persona

Voice & behavior of the school's assistant

Knowledge sources

What the assistant is grounded in
πŸ” Security note: the β€œViewing as” switcher and these scopes are the convenience layer. The real boundary is server-side β€” every API request is re-checked against the caller’s role + scope (school, department), so a lower role can’t reach other data even by calling the API directly. See Architecture β†’ Server-side authorization.

Roles & Permissions

Who can edit what β€” the CRM access model

Publishing Workflow

Draft β†’ review β†’ publish, with audit trail
✍️ Contributor draftsβ†’ πŸ‘οΈ Editor reviewsβ†’ βœ… Admin publishesβ†’ 🌐 Live site + Emperor AI update

Integrations

The systems a school site must connect to
🧩 The two-part setup. Part 1 is the public site you can open in a tab. Part 2 is this CMS. They share one content model β€” in production a database behind a headless API. This panel documents the full backend the school would run.

System Architecture

What ships when this goes to production