Please note: this article is for users with a System Admin role.
As you begin to fill out your user import template, you may be curious about how fields related to users will impact data and reporting later on. This article will detail the link between user fields and Grow reports, as well as share best practices for filling out the user import template.
In addition to required information fields like name and email, Grow's user import template includes various optional fields that can be associated with users. Importing more fields related to users will help you analyze reports using the data points that are most relevant to your network.
System administrators can determine which information should appear on reports, versus only on the user profile, in System Settings. The most frequently used optional fields, with recommended best practices, are below.
- Primary Coach: Populating this field with observer emails will allow users to see which observer is primarily responsible for which observee's feedback. Numerous Grow reports have a toggle to filter by primary coaching load, so uploading primary coach streamlines the coach's experience.
- Grade: Grow reports can be filtered by grade level. The user template allows you to choose a grade from the drop-down options provided. If a user is involved with more than one grade, please just pick one. Writing down two grades will not upload into the system correctly, and we instead recommend using something like "Multiple Grades".
- Course: Grow reports can be filtered by course. Make sure that course language is consistent from user to user. For example, "Physical Education" and"PE" will upload as two different courses. Additionally, each user can only have one course. Writing down more than one will not upload correctly and we instead recommend using something like "Multiple Courses".
- User-Type: Grow reports can be filtered by User-Type(s), which is another field for group your users into categories. Some common user-types include years at the network or instructional versus non-instructional. Similar to the above fields, language must be consistent from user to user or multiple user-types will be created.
Do you need more information?
Click the Support and Feedback button or email us at growsupport@schoolmint.net
Comments
0 comments
Please sign in to leave a comment.