Staff Data
Schools using nVision
For schools that use nVision, Staff Data in SchoolMessenger actually comes from what's in nVision as this system is considered the "source of truth" when it comes to staff data.
In regard to data in nVision, only records for staff assigned to an Employee Group where the "Telephone Notification" checkbox is checked, will ever flow automatically into SchoolMessenger:
That means if the checkbox above isn't checked for an employee group that a staff member is assigned, their data won't flow into SchoolMessenger. The following table illustrates how data stored in nVision "maps" to data in SchoolMessenger.
Column ID | nVision Tab or Module | nVision Field Name | SchoolMessenger Field | Notes |
1 | Main Employee Screen | EmployeeID | ID # | This is populated with the staff members "Employee ID" as issued by nVision.![]() |
2 | Main Employee Screen | First Name and Last Name | Name | The value that appears in SchoolMessenger is a concatenation of the First Name and Last Name fields in nVision.![]() |
3 | N/A | N/A | Language Preferred | Defaults to English for all staff members as nVision has no field to identify the primary language that staff speak. |
4 | N/A | N/A | Grade | This field is used only for student records, therefore it's left blank for staff records. |
5 | N/A | N/A | Attendance Date | This field is used only for student records, therefore it's left blank for staff records. |
6 | N/A | N/A | Contact Type | This field is defaulted to "Staff" for all staff records in SchoolMessenger. |
7 | Appointment Information>Position Appointment tab | Employee Group | Title | The name of the "Primary Employee Group" that a staff member is assigned to in nVision becomes their "Title" in SchoolMessenger.![]() |
8 | Appointment Information>Building Assignment tab | Building | School | The "Buildings" that an employee is assigned to based on their primary employee group in nVision, becomes the "School(s)" they are assigned to in SchoolMessenger. ![]() **Staff not assigned to a specific building, are given a "School" in SchoolMessenger of "District Office" instead. |
9 | Addresses Tab | Street 1 Street 2 City, State, Zip | Address | The value that appears in SchoolMessenger is a concatenation of the Street 1, Street 2, City State and Zip fields in nVision, for the address set as "Default" (Primary).![]() |
10 | Contact Information Tab - "Phone Numbers" area | Phone Number marked as "Default" and not "Private" | Phone 1 | The value that appears in the "Phone 1" field in SchoolMessenger is the phone number checked as "Default" in nVision assuming that it's not also checked as "Private".![]() |
11 | Contact Information Tab - "Phone Numbers" area | First Phone Number not marked as "Default" and not "Private" | Phone 2 | The value that appears in the "Phone 2" field in SchoolMessenger is the first phone number in nVision that's not checked as "Default" assuming that it's also not checked as "Private". |
12 | Contact Information Tab - "E-Mail Addresses" area | Email Address marked as "Default" | Email 1 | The value that appears in the "Email 1" field in SchoolMessenger is the email address checked as "Default" in nVision.![]() |
13 | Contact Information Tab - "E-Mail Addresses" area | First Email Address not marked as "Default" | Email 2 | The value that appears in the "Email 2" field in SchoolMessenger is the first email address in nVision that's not checked as "Default" |
14 | Contact Information Tab - "Phone Numbers" area | Phone Number marked as "Default" and not "Private" with a description of "Mobile" or "Cell" | SMS 1 | The value that appears in the "SMS 1" field in SchoolMessenger is the phone number with a description of "Mobile" or "Cell", if and only if it's also checked as "Default" in nVision assuming that it's also not checked as "Private". |
15 | Contact Information - "Phone Numbers" area | First Phone Number not marked as "Default" and not "Private with a description of "Mobile" or "Cell" | SMS 2 | The value that appears in the "SMS 2" field in SchoolMessenger is the is the first phone number with a description of "Mobile" or "Cell", if and only if it's also not checked as "Default" assuming it's also not checked as "Private". |
In situations where there is purposely no staff record for a given person in nVision (i.e. Shared Staff), schools can still enter staff records into Schooltool and have them pass into SchoolMessenger, but those records then must be "flagged" properly in order for the record to make it's way into SchoolMessenger.
Below is information on what fields must be set in order to properly "flag" Faculty Records in Schooltool, so that they are sent to SchoolMessenger:
- The "Email" field that appears at the top of the employee's record, cannot be blank --AND-- cannot be an address that contains @edutech.org
- In the "Faculty Information" area of the staff record, ONE of the following must be true:
- The "Department" field must be set to "EduTech"
--OR-- - The "Type" field must be set to "Shared Staff"
- The "Department" field must be set to "EduTech"
Schools using Other HR Systems
At this time, schools that do not use nVision as their HR system, must instead use Schooltool as the "system of truth" when it comes to staff data. When staff data residing in the Faculty Module of Schooltool is used to send data to SchoolMessenger, records for staff members will pass to Schooltool if and only if the following situations are ALL true:
- At least one "school level" within one building must be checked
- The "Active" checkbox must be checked
- The "Type" field must be set to a value other than "NONE"
- The "Department" field must be set to a value other than "SELECT ONE", however the following departments if selected will also omit the record from being sent to SchoolMessenger by default:
- Other
- EduTech
- The "Faculty ID" and/or "Universal FacultyID" field(s) must contain a value
IMPORTANT: Data residing in Schooltool Faculty Records is not considered valid until ALL of the criteria above has been met.