For administrators with Remind Hub using CSV format 2.0.

Follow the instructions below to properly format the 5 CSV files that are required every time you share rostering data with Remind via SFTP.

In this article we will also cover: 

• Tips to avoid the most common problems
• How to format your CSV files - examples and downloadable templates included
• FAQ

Tips to Avoid Common Problems

Include the following 5 CSV files every time you send new rostering data to Remind via SFTP. Every column header is a required part of each CSV, but for some columns, the cells below the header can be left blank.

1. schools.csv 

This required file establishes school_ids which are used in subsequent CSV files to associate users and classes to the correct school.
See the example file or download the template

school_id  

• Unique ID used in subsequent CSV files to match users and classes to schools.
• Must be unique for every school in the district; there cannot be multiple schools with the same ID.
• Can include any combination of characters and numbers.
• Data required

school_name  

• Name of the school, used internally to match the CSV data with the correct school on Remind.
• Can include any combination of characters and numbers.
• Data required

2. classes.csv

This required file is used to create classes and associate them with a school in Remind. 
See the example file or download the template

class_id

• 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.
• Data required

school_id

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

class_name

• This is the class name that will display in Remind, which class owners will be able to edit via their own Remind account later.
• 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.
• Data required

semester

• This will be used for future features on Remind. For now, it can be used to help internally 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.

3. enrollments.csv

This required file is used to enroll people in classes. Classes can have multiple owners. 
See the example file or download template

class_id

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

user_id

• Must correspond to user_id in users.csv file.
• Data required

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.

4. users.csv

This required file is used to create Remind accounts for administrators, teachers, non-teaching staff, students, and parents.
See the example file or download the template

IMPORTANT: Do not include emergency contacts. Only include students, parents, teachers and administrators, and staff.

user_id

• 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.
• Data required

first_name

• User’s first 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.
• Data required

last_name

• 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.
• Data required

preferred_language

• 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 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. 

• 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 be blank. Users can add a preferred language to their account at any time.

contact_point_1

• Contact point is either an email or phone number.
• Must be unique between users. For example, students and parents cannot share the same phone number. If they do, it will not hold up the sync, but 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 that you do not assign work phone numbers to any user as these numbers are often shared by multiple users across multiple districts. 
• Phone numbers can be with/without parentheses, hyphens, and/or an international area code. Examples: (444) 432-1234, 4444321234, 444-432-1234, +1 (444) 432-1234
• Phone numbers cannot have an extension number as we currently do not ingest extensions. For example, we will not accept (444) 432-1234x7272. 
• 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.
• Emails must be formatted as "_@_._"
• Administrators, staff, and teachers must have at least one email.
• Parents must have at least one phone or email.
• Students may not have contact points, but without them, their accounts will be informational, and not contactable.
• 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 "administrator" role for individuals who manage a school, the “teacher” role for individuals who are educators in your organization and manage classes, and choosing the "staff" role for people who are non-teaching members such as coaches and guidance counselors. Learn more about our roles here.
• "Student", "parent", "administrator", "teacher", "staff", "teacher,staff", "parent,teacher", "parent,staff", "staff, teacher, parent", "administrator,parent" and "administrator,teacher,parent" are the accepted value combinations. 
  
  • Students cannot have the staff role at the moment.
• Data required

dob

• Student date of birth.
• Required for all students, but can be left blank for parents and teachers.
• Accepted formats: MM/DD/YYYY or YYYY/MM/DD.

grade

• Student grade level, which 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

• Used to make personalized and automated messaging.
• 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.

5. school_enrollments.csv

This required file can be used to add a user to a school without associating them with a class, such as support staff, specialists, and administrators.
See the example file or download the template

IMPORTANT: If you do not need to use this file, you still need to upload it with the column headers; just leave the rows below blank.

school_id

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

user_id

• Must correspond to user_id in users.csv file.

school_role

• 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. 

NOTE: To add a user to multiple schools, add a row for that user for each school.

Examples and templates to download

Once you have properly formatted all 5 CSV files, you are ready to transfer your CSV files using SFTP. Follow steps 3-6 on this resource: Transfer CSVs to Remind.

FAQ

Can a user have multiple roles?
The only roles that can be shared are parent and teacher. To do this, put "parent, teacher" under role in the users.csv file.

What happens when phone numbers and emails get updated in the SIS?
When contact information is updated in your SIS, it will be updated in Remind so long as your CSV data files are updated and reuploaded. Please note that this will not remove any contact points that were confirmed or added directly to an account by the account owner.

What’s the difference between user_id and student_number?
Students, parents, and teachers have a user_id, whereas only students can have a student_number. You can make user_id and student_number the same if it’s easier to format.

Can a class have multiple teachers?
Yes, just list each teacher as "class owner" instead of "participant" in the enrollments.csv file.

Return to top