Skip to content


Product Ideas Portal

SMS 2.0 School Management System


When you chose Skyward, you chose a partnership over a purchase, a user-centered solution over a canned system, and a better experience over the status quo.



Customer Feedback for the

SMS 2.0 School Business Suite


Share your ideas here and watch them evolve into the future of our products and services. We can't respond to all of them, but we are committed to reading every single idea.



Customer Feedback for the

SMS 2.0 Student Management Suite


Share your ideas here and watch them evolve into the future of our products and services. We can't respond to all of them, but we are committed to reading every single idea.

Cory Calvert

My feedback

1 result found

  1. 9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Upon Clarification, I have created a PR (5564535) to add individual fields in Request Changes for Email Addresses.


    Keep an eye out for emails regarding this product idea!


    Thank you!


    Erik O.

    An error occurred while saving the comment
    Cory Calvert commented  · 

    It looks like this request has been hanging out there for a long time now. This is actually pretty important from a security perspective, as many districts use the primary email address for SSO authentication with SAML. Right now, you can either prevent users from changing any email addresses at all, which keeps the HR department from having an up-to-date secondary contact email, or you can allow users to change all email addresses, including their primary email address, which allows users to effectively change their own username in the system (depending on SSO configuration).

    I just had to fix a problem with one of our employees getting locked out of HR/Finance after they updated their own email address, which was set to Auto-Approve in Request Change Setup. I could imagine some districts allowing a combination of SSO and LDAP or local authentication for users, and in that case, if a privileged user who normally logs in with LDAP or a local account didn't have their school email address in the primary email address field, a less-privileged user could simply change their own primary email address to that of the high-privileged user and then reauthentication to the HR system as the high-privileged user through SSO. This seems like a potentially serious security issue.

    Cory Calvert supported this idea  · 

Feedback and Knowledge Base

Feedback and Knowledge Base