school_id (data required)

• A unique ID used in subsequent CSV files to match users and classes to schools.
• There must be a unique ID for every school in the district; the file cannot contain multiple schools with the same ID.

school_name (data required)

• Name of the school. It is used internally to match the data with the correct school in your Remind Hub.
• Can include any combination of characters and numbers, such as "Markham Elementary 2".
• School names cannot exceed 60 characters.

class_id (data required)

• Unique ID used in other CSV files to match users to classes.
• Must be unique for every individual class in the district.
• Can include any combination of characters and numbers.

school_id (data required)

• Must correspond to a school_id in the schools.csv file.

class_name (data required)

• This is the class name that will be displayed in Remind. Class owners can edit their class name, which cannot exceed 255 characters.
• It’s recommended to have unique names for each class period to help class owners differentiate between their classes.
• Can include any combination of characters and numbers.

Semester (header required)

• This will be used for future features on Remind. For now, it can be used to help our internal team to troubleshoot and differentiate between classes.
• Can include any combination of characters and numbers.
• The header is required, but adding data to this column is optional.

class_id (data required)

• Must correspond to a class_id in the classes.csv file.

user_id (data required)

• Must correspond to user_id in users.csv file.

class_role

• This determines who in the class is the owner — the person who has permission to send announcements (usually the teacher).
• Each class must have at least one owner.
• Classes can have multiple owners. You can assign a maximum of twenty owners per class. 
• Accepted values: "owner," "participant."
• If this section is left blank, the default role will be participant.

user_id (data required)

• Unique ID used in other CSV files to create enrollments and parent relationships.
• Must be unique for every user in the district.
• Can include any combination of characters and numbers.

first_name (data required)

• User’s first name.
• Be sure to remove apostrophes and quotes. If you cannot remove apostrophes and quotes, wrap the data in quotes.
• Can include any combination of characters and numbers.
• The display name for users under 13 will appear as their first name and the first initial of their last name in Remind. Ex. Jay Easton will appear as Jay E. 

last_name (data required)

• User’s last name.
• Be sure to remove apostrophes and quotes or elect to access the data wrapped in quotes.
• Can include any combination of characters and numbers.

Preferred_language (header required)

• Messages that users receive will be translated into their preferred language. If the preferred language is updated by the user, teacher, or administrator, it will take precedence over the data in the CSV file.
• The header is required, but adding data to this column is optional.
  • If you do not provide this data, the preferred language for all accounts will default to English.
  • Users can add their preferred language to their account at any time.
• The only values we accept for the preferred_language column are any two-letter ISO-639-1 or BCP-47 code or three-letter ISO-639-2 code you can get from this list here. 

contact_point_1 (data required for all roles except students)

• Contact points are either an email address or phone number.
• Administrators, staff, and teachers must have at least one email.
• Parents must have at least one phone number or email.
• Contact points must be unique between users.
  • For example, students and parents should not share the same phone number. This prevents accidentally rostering students with the same phone number as their parents. This can also cause unwanted merges between parent and student accounts.
  • If they’re rostered in with the same phone number, the phone number will be given to the user with the highest role (teacher -> parent -> student).
  • If users have the same role, the contact device will be assigned in alphabetical order according to their source id.
• We also highly recommend not assigning work phone numbers to any users, as multiple users across multiple districts often share these numbers.
• Phone numbers can be with/without parentheses, hyphens, and/or an international area code.
  • For example, (444) 432-1234, 4444321234, 444-432-1234, or +1 (444) 432-1234.
  • Phone numbers cannot have an extension number.
  • For example, we will not accept (444) 432-1234x7272. This will cause an error to occur when creating user accounts.
• This can remain blank if other contact point columns are filled in.
  • For example, some organizations use contact_point_1 for an email address, contact_point_2 for a cell number, and 3 for a home number, etc.
• Phone numbers must be from the US or US territories, including Puerto Rico, American Samoa, Guam, the Northern Mariana Islands, and the U.S. Virgin Islands.
• Students may not have contact points, but without them, their accounts will only be contactable via Remind.
• To add a phone number to students under 13, it is required for the student to be connected to a parent with a different phone number. This helps to prevent accidentally rostering students with the same phone number as their parents.

contact_point_2, contact_point_3, contact_point_4, contact_point_5

• Can be left blank or used to provide additional contact points for a user.

role

• This determines the role and permissions that a user will have on Remind. 
• We recommend choosing the following roles,
  • "administrator" - This role is for individuals who manage a school.
  • "teacher" - This role is for individuals who are educators or will manage classes.
  • "staff" - This role is for non-teaching members, such as coaches and guidance counselors.
• The following are accepted value combinations for users:
  • "administrator"
  • "student"
  • "parent"
  • "staff"
  • "teacher,staff"
  • "parent,teacher"
  • "parent,staff"
  • "staff, teacher,parent"
  • "administrator,parent"
  • "administrator,teacher,parent"
• Students cannot have the staff role at this time.
• Learn more about our roles here.

dob (data required for students only)

• Date of birth is required for all students, due to COPPA; click here to learn more.
• This can be left blank for parents and teachers.
• Accepted formats: MM/DD/YYYY or YYYY/MM/DD.

grade

• Student grade level. This can be used to filter students on the People list.
• Recommended for students, but not required — can be left blank.
• Accepted values: PK, KG, 01 through 12, and Other.
• A student can only be associated with one grade.

student_number

• Can be used to make personalized and automated messages.
  Including this field also allows students to claim their rostered account using their phone number. Learn more.
• Recommended for students, but not required — can be left blank.
• What’s the difference between user_id and student_number?

parent_id_1, parent_id_2, parent_id_3, parent_id_4, parent_id_5

• Forms the student-parent relationship, which makes it easier for teachers to identify parents and students.
• Must correspond to a parent's user_id in the users.csv file
• Strongly recommended for students (especially for advanced messaging), but not required — can be left blank.

school_id (data required)

• Must correspond to a school_id in the schools.csv file.

user_id (data required)

• Must correspond to user_id in users.csv file.
• To add a user to multiple schools, add a row for that user for each school.

school_role (data required)

• Put "participant" for a user with either the student, parent, or teacher role.
• Put "staff" for users who only have the staff role.
• Put "administrator" for users with the admin role. 
• If a user has the teacher and the staff role for the same school, add them twice in the school_enrollments file - once as a  "participant" and once as a "staff" for the same organization.