Filename: /automated/school_staff.csv

Inclusion criteria: All staff that should have access to SchooLinks

Minimum Upload Frequency: As this data changes -this will be important for both creating new accounts and removing accounts where users should no longer have access to student data

<aside> 💡 Note that at least one of staff_id, staff_sis_id, or teacher_number must be passed so we have a unique key for staff. If you will be sending caseloads through the caseloads.csv schema you must make sure that you have included the type of staff identifiers that will be passed for caseload creation

</aside>

Download fillable template here:

school_staff.csv

Staff Schema Columns

School Staff Access Types:

Indicates how a user's access will be scoped.

• If district is passed, the user will have access to all students in the district. You can optionally supply grades in the "grades" column to further restrict this user's district-wide access to a subset of grades.
• If school is passed, you MUST provide the list of school codes to which this user can access. You can also provide a list of grades to which the user's access will be restricted within the schools they have access to
• If caseload is passed, this means that a user will need to have students explicitly assigned to one of her/his caseloads. For example, a counselor can be given a caseload of students for course scheduling or a teacher can be given a "caseload" of students to guide in his/her career planning class. This can be done in the SchooLinks School Admin Management UI after School Staff creation or through the caseloads.csv data upload but not both (see note in Caseloads Schema).

Manual Staff Accounts

• Though we discourage it, It is possible to create manual staff accounts if you have District Project Manager role (gives access to the Staff Account Management).
  • We do not require staff identifiers to be populated when creating staff manually, mainly because it’s not really clear to most people what field they would use for each identifier
• If an account is manually created and we match the email of a manually created account, then we automatically turn the record to a synced record. We do this because this is a security best practice — it allows us to both update and deactivate accounts if they subsequently drop out of a sync.
  • ⚠️ this can create issues if manual accounts are added and then removed because it will deactivate accounts that were initially created manually