Skip to content

District Administrator Responsibilities

The District Administrator is the district's primary operational contact for schoolboard.net. The role combines first-line user support, access administration, content oversight, and coordination with schoolboard.net Support.

Provide first-line district support

District Administrators are normally the first point of contact for:

  • Board Members who cannot sign in or access expected materials;
  • Group Administrators who need membership, access, or workflow assistance;
  • users who need account information corrected;
  • questions about which district Group or administrator owns content; and
  • reports that an agenda or other content appears to be missing.

Resolve routine district-level questions when possible. Contact schoolboard.net Support when the issue involves platform behavior, security-controlled access, or a correction that cannot be made safely with District Administrator tools.

For questions about spelling assistance in Drupal content blocks, use Browser Spell Check and Proofreading. District technical support may need to change a managed-browser or device policy when the user cannot activate spell checking.

Serve as the primary schoolboard.net contact

The District Administrator coordinates with schoolboard.net Support on behalf of the district. This includes:

  • reporting problems with enough detail to investigate;
  • requesting security-controlled administrator changes by email;
  • coordinating staff transitions and access changes;
  • arranging assistance with templates or district-specific workflows; and
  • sharing approved operational questions and feedback.

For support requests, include the district, affected user or Group, page or agenda title, relevant date and time, expected result, actual result, and screenshots when available.

Manage user accounts and access

Within approved district policy, District Administrators can:

  • search for an existing user before creating another account;
  • add and edit user accounts;
  • correct approved account information;
  • activate, block, or restore access;
  • review roles and Group memberships;
  • add or remove Group memberships; and
  • verify that users have only the access required for their responsibilities.

Removing access may require more than one action

Removing a Group membership is different from blocking a user account. Follow the appropriate offboarding procedure and verify the final account status, roles, and memberships.

Manage Group Administrator access

District Administrators may assign an existing user as a Group Administrator for an approved Group and may remove that Group membership when access is no longer authorized.

Apply least access:

  • assign only the required Group;
  • grant Group Administrator access only when approved;
  • review access when responsibilities change; and
  • avoid shared administrator accounts.

Understand District and Group Administrator roles

A District Administrator is not automatically a Group Administrator.

District-wide administrative access and Group-specific administration are separate. A District Administrator may manage a Group's day-to-day content and membership only when assigned to that Group with the appropriate Group Administrator access.

Confirm both levels of access

When a District Administrator needs to prepare an agenda or manage Group content, confirm that the person is also assigned to the correct Group as a Group Administrator.

When editing an agenda, follow Edit locks and safe agenda editing. Saving preserves the work and releases the lock; use Unlock only when no changes were made.

Oversee Groups and district content

District Administrators can:

  • review existing Groups and their assigned administrators;
  • create approved Groups using the correct permanent Group type;
  • edit Group information when authorized;
  • locate site-wide content through the administrative Content list;
  • verify that every agenda belongs to the intended Group; and
  • use the newest revision when several entries have the same title.

The Group type cannot be changed after creation. Stop and confirm the correct type before saving a new Group.

Edit Group and public home-page content

District Administrators may edit Group content only when they have also been assigned as a Group Administrator for that Group.

The public site home page belongs to the protected site-home-page Group. By default, schoolboard.net Support administers this Group so an administrator does not inadvertently publish content to the district home page.

To edit the public site home page:

  1. Submit an email request to schoolboard.net Support.
  2. Request temporary Group Administrator access to the site-home-page Group.
  3. Make and verify the approved change.
  4. Email Support to request removal from the Group when the work is complete.

Remove temporary access

Request removal after the home-page change is complete. Limiting continuing access reduces the risk of accidental public changes.

Protect district security

District Administrators are responsible for:

  • using individual administrator accounts;
  • applying least access;
  • verifying identities and authorization before changing access;
  • promptly updating access when staff responsibilities change;
  • protecting confidential Board materials;
  • documenting security-controlled requests by email; and
  • asking before making an uncertain access or privacy change.

Know what requires schoolboard.net Support

Only schoolboard.net Support may add, remove, or modify a District Administrator role assignment. Submit the request by email from an authorized district representative.

schoolboard.net also provisions the ATM (Administrative Team) Group and assigns the designated District Administrator as its Group Administrator during setup. Requests involving security-controlled administration of ATM or the protected site-home-page Group must be submitted by email.

Maintain two or three approved District Administrators so the district has coverage during absences and staff transitions without granting unnecessary district-wide access.

Document local responsibilities, identify the primary contact, and promptly notify schoolboard.net Support when that contact changes.