← All examples

Completed case study / Staff access

From blocked access
to usable schedules.

A staff member working across 2 schools needed student schedules to support their work. The account needed the right school access, a working sign in, and a final check with the person using it.

2 schoolsOne existing account
Viewing accessMatched to the staff member’s role
Staff confirmedThe requested access worked
The completed result

The staff member could get to
the schedules they needed.

Missing school access was added, existing access was preserved, and the remaining sign in problem was resolved. After receiving instructions and being asked to check the result, the staff member confirmed that it worked.

A staff member supporting students across 2 schools needed to view their schedules in PowerSchool. The request moved from IT to the school’s data support function because the issue involved access within the student information system.

The first access change did not finish the job. The staff member still could not sign in successfully, and a required school role was missing. Support continued until the person could use the access.

The work

Follow the problem
through to the person.

The work combined account review, a targeted correction, clear instructions, and confirmation from the staff member.

  1. Clarify the task.

    The request established which school schedules the person needed. The existing account and school access were reviewed.

  2. Correct the missing access.

    The missing viewing role was added for one school. Access to the other school was checked and preserved.

  3. Resolve the sign in barrier.

    The remaining login problem was addressed, with instructions for the correct sign in page and switching between schools.

  4. Ask the person to check.

    The staff member was asked to sign in and check the schedules they needed. Their reply confirmed that the access worked.

How completion was checked

A saved change.
A successful user check.

The record includes the school access correction, confirmation that existing access was preserved, follow up on the sign in issue, and the staff member’s reply confirming success.

This case comes from professional school operations work behind First Bell. School and staff identities are omitted for privacy. The outcome is paraphrased from the original support record.