Skip to main content
Who this is forSchool Admin

School Administrator Guide

The School Administrator role exists for the work a school does on its own, on top of what the district configures. In practice that comes down to two things: assignments, when the district delegates them, and school-wide prompts, when a school wants its evaluators working from a shared set.

Most other configuration arrives from the district, and most schools accept it as-is.

:::note Head Principals already have this role The Head Principal role automatically includes School Admin, so at many schools there's no separate School Admin — the head principal does this work. See Roles in eVAL. :::

Your Main Task: Assignments

Districts commonly delegate evaluator assignments and plan types to schools. When yours does, this is your real start-of-year work: give every evaluatee at your school an evaluator and a plan type.

Principals can do this too. Delegation goes to the school, not to a specific role — School Admins and principals both work the same Assignments page.

See Assignments & Plan Types for the steps.

:::tip Can't edit assignments? Your district is handling them centrally. That's a district setting, not a permissions problem — ask your District Admin to delegate to your school. :::

School-Wide Prompts

Any evaluator can create their own prompts, so a school-level prompt set is about sharing a common set across the school's evaluators rather than enabling something otherwise impossible.

It's most useful at a larger school where three or four principals evaluate teachers and everyone should be working from the same questions. School prompts are additive — they combine with the district's rather than replacing them.

See Prompt Bank & Resources.

What Else You Can Do

AreaWhat You Can Do
SettingsOverride district settings where allowed — though most schools accept the district defaults
ResourcesAdd school-level resources for evaluations
OversightMonitor evaluation progress at your school

What You Control vs. District

TaskYouDistrict Admin
Select evaluation frameworksNoYes
Enable/disable optional modulesIf allowedYes
Override module settingsIf allowedYes
Assign evaluators & plan typesIf delegatedYes
Configure DTE/DPE assignmentsNoYes

Key Concepts

Settings Inheritance

Your settings layer on top of district settings. See How Settings Are Inherited:

  • Additive areas (prompts, resources): Your additions combine with district's
  • Override areas (module settings): Your settings replace district's (if allowed)

School Override

For each optional module and setting, the district controls whether you can override. Look for the "Allow Schools to Override" toggle - if it's not enabled at the district level, you'll see the setting but can't change it.

See Modules and Settings for what each setting does.

Teacher Evaluations Only

School-level settings only apply to teacher evaluations conducted by school principals. They're bypassed for:

  • Principal evaluations (always use district settings)
  • Teacher evaluations by DTEs (district-level evaluators)

See Settings Inheritance for the full matrix.