Your Profile

The student/staff portal intentionally does not include a self-service profile editor. Your account record — name, email address, building, grade level, username, guardian contacts — is managed by your school district's tech and registrar teams, not by you. This is on purpose: the same record drives access controls, attendance reports, and parent communications, so changes have to be made centrally where they can be verified.

This page explains what's on file and how to get it corrected.

What your district has on file

Common fields stored on every end-user account:

• Name — first, last, and (where applicable) preferred display name.
• Email address — usually your school-issued address. This is where the portal sends ticket updates, password resets, and any other notifications.
• Username — what you'd type into the Email box on the sign-in screen if your district uses username-based sign-in instead of email.
• Building — your home school within the district. Drives which devices and accessories show up in your tech office's pickers.
• Grade level — for students; usually blank for staff.
• Guardian contacts — name + email/phone for the parent(s)/guardian(s) tied to a student account. Used for the parent portal magic-link sign-in.
• Custom fields — anything else your district has set up — bus route, lunch program, e-Portal classification from your SIS, etc. These are read-only on the portal.

You see most of these reflected in places you visit (e.g. your name shows in the top-right corner; your district shows on the sign-in screen). But the portal doesn't have an "Edit Profile" button.

What you CAN change on your own

Just one thing on most installations: your sign-in password — through the Forgot Password? link on the sign-in screen. If your district uses Single Sign-On (Google, Microsoft, ClassLink), your portal password isn't used for anything — your password lives with the SSO provider, and you change it through their account-settings page (e.g. myaccount.google.com).

That's the entire self-service surface for end users. Everything else is admin-managed.

How to get something corrected

The right contact depends on what's wrong:

• Name spelling, preferred name, gender marker, grade level, building — these come from your district's Student Information System (SIS). Talk to your school's registrar; they update the SIS, and the next OneRoster sync pulls the corrected value into Manage1to1.
• Email address that's bouncing notifications — your tech office can update the address on file directly.
• Guardian contact missing or wrong — your registrar handles this; SIS data again.
• Username login isn't working — your tech office can verify the username on your account or reset it.
• Custom fields with wrong values — depends on the field. SIS-sourced fields go through the registrar; admin-entered fields go through your tech office.

Why does it work this way?

Two reasons:

1. Compliance. School-record changes (especially anything tied to legal name, guardian information, or age-of-majority status) require district verification. Letting students edit those fields themselves would break federal record-keeping rules.
2. Single source of truth. Most districts already have your data in their SIS. Letting two systems both be editable produces inconsistencies — and those inconsistencies show up later in parent communications, ID cards, and report cards.