Section 1(1)(gg) of the School Act defines a “student” as an individual who is:

The Student business object contains all personal information about the student.

This business object includes the following attributes:

The following rules are applied to control access to view/add/edit the Business Object records.

When requesting updates for Student data, the Student is generally available to the PASI Client if their organization is O.1¹⁾ or their organization is associated to the student By Student Creation, By Current School Enrolment, or By Last School Enrolment.

However, if the PASI Client’s organization is O.1 and they have been assigned the High School Student Sync User role, the students available to the PASI Client are limited based on the Synchronization Status of the ASN (Note: for Secondary ASNs, the Synchronization Status of the Primary ASN should be considered instead of the Synchronization Status of the Secondary ASN).

Only those students who also have a Synchronization Status of On or Enabled are eligible for these PASI Clients.

Access to a specific Student (or Alberta Student Number) is governed by the organization requesting student information. An organization can access a student if the organization meets any one of the following criteria:

• The organization is associated to the student By Last School Enrolment, By Current School Enrolment, By Student Creation, or By Ministry
• The organization is not considered a Authority
• The organization is considered a Authority with a Low restriction level and Has a Historical School Enrolment for the student.

Having access to a student allows the organization to confirm that the student/ASN exists in PASI and is required in order to see any demographic information associated to the student.

It is possible for an organization to have Record Ownership of records attached to students that the organization does not have access to. In these cases, while the organization may be able to update the records they own, they cannot view any student demographic information for the student.

When accessible, the following rules are applied to specific data elements on the record:

There are no access rules applied when creating a new student record.

Updating Student records are done by calling specific services to update specific attributes of the student. The attributes below can be updated by a PASI Client.

See Student Name Data Access Rules for details.

See the Student Name Data Access Rules.

In order to update the Is Deceased or the Date of Death data element, the:

• PASI Client must have the Submit Student User role, and
• Organization must be associated to the student By Last School Enrolment or better⁵⁾⁾ .

In addition, when being updated via PASIprep, the:

• PASIprep user must have the PASIprep Level 02 Permission - Manage Student Information permission.

See Student Name Data Access Rules for details.

See Information Disclosure Restriction Data Access Rules for details.

See Student Address Data Access Rules for details.

In order to update the Maturity Date or the Maturity Reason, the:

• PASI Client must have the PASI System User role.

In addition, when being updated via PASIprep, the:

• Organization must be associated to the student By Last School Enrolment or better⁶⁾⁾ .
• PASIprep user must have the PASIprep Level 04 Permission - Manage Mature Student Status permission.

See Student Phone Number Data Access Rules for details.

In order to update the Preferred Name data element, the:

• PASI Client must have the Submit Student User role, and
• Organization must have Access to the Student, and
• Organization must be associated to the student By Exam Registration, By Last School Enrolment or better⁷⁾⁾ .

In addition, when being updated via PASIprep, the:

• PASIprep user must have the PASIprep Level 02 Permission - Manage Student Information permission.

In order to update the Preferred Phone Number data element, the:

• PASI Client must have the Submit Student User role, and
• Organization must be associated to the student By Last School Enrolment or better⁸⁾⁾ .

In addition, when being updated via PASIprep, the:

• PASIprep user must have the PASIprep Level 02 Permission - Manage Student Information permission.

In order to update the Primary Language Spoken at Home data element, the:

• Organization must have access to view the Primary Language Spoken at Home as outlined above⁹⁾

In order to update the Section 23 Eligibility data element, the:

• PASI Client must have the Submit Student User role, and
• Organization must be associated to the student By Last School Enrolment or better¹⁰⁾⁾ .

In addition, when being updated via PASIprep, the:

• PASIprep user must have the PASIprep Level 02 Permission - Manage Student Information permission.

In order to update the Gender (Student) data element, the:

• Organization must meet the Access to a Record rules above, and
• Organization must be associated to the student By Ministry, By Student Creation, By Current School Enrolment, By Last School Enrolment, or By Exam Registration.

In order to update the Acknowledgement Status data element of a student Core Alert, the:

• PASI Client must have the Submit Student User role, and
• Organization must be associated to the student By Last School Enrolment or better¹¹⁾ , and
• Organization must have access to the record associated to the Core Alert.

In addition, when being updated via PASIprep, the:

• PASIprep user must have the PASIprep Level 02 Permission - Manage Student Information permission, and
• PASIprep user must have access to the record associated to the Core Alert.