User Types
The app needs data for the following types of users:
Instructors
Advisors
Admin (all other non-student users; e.g., Registrar’s Office staff who are not advisors)
Students should not be included in the user feed as they are supplied in the student basic feed (unless they also serve in an administrative role as instructors, advisors, etc).
User
The user feed contains all non-student users who will access the Stellic platform (advisors and other administrative users); students are sent in the student_basic feed only (though a user who is both a student and administrative user should be included in the user feed if a common “username” value is used in your SIS; their name and details will be combined from both feeds for display in Stellic).
Individuals who only have an “instructor” type value will typically not have an account provisioned but simply be used to do name matching/display for sections from the schedule_basic feed. Institutions using Care functionality can have accounts created for those users, enabling them to login and use the platform (permissions for those users will be set accordingly per permissions setup).
User Activation: User account creation and activation are separate processes (simply because a user is in the feed and “loaded” into Stellic does not grant automatic access). The Stellic integration team will work with you to activate users at an appropriate point in the implementation process. SuperAdmin users can always manually activate users once their account is created in the platform.
Expected feed filename: user.csv
Samples: CSV
Field | Description | Requirement |
| Unique identifier for a user. These values must match the user attribute that is passed via SSO (often a username or ID number). This value should not change over time (should persist through name changes, changes in employment status, etc. so Stellic can continue to use it to match on the same value across time and data feeds). This value will be visible in the platform (Staff tab) but will be replaced with the user’s name in student information (for instructors and advisors). Examples: “567937”, “j563h254” | required |
| The SIS id number for the user. The column is required in the data feed. However, this is not a required value but is very helpful if your institution uses this value for searching for users (either username or id can be used for searching by SuperAdmins for permission setup, along with a user’s name). Examples: “d815017” | recommended (column required) |
| The official institutional email address for the user. This column is “required” since it is necessary for data sync of this feed to operate and a user’s email must be present for notifications within the platform. A user record with no email still allows access to the platform but functionality triggered by emails like notifications will not occur until a valid email address is included in a following data sync.
Examples: “jterry@stellic.edu” | required |
| List of types where valid types are: [‘instructor’, ‘advisor’, ‘admin’]
Multiple values should be pipe-delimited. Other types are also possible but require development of advanced functionality. Check with your Stellic integration specialist for more details. | required |
| The user’s first name. | required |
| The user’s last name. | required |
| If different from the official/legal first name. This value will replace the first_name value above if provided (and the ‘first_name’ value will not be loaded). | Optional |
| The current teaching location/branch campus to which the user belongs. This value must match a value supplied in the id column of the Campus tab of the configuration sheet (a foreign key to this column). | Optional |
| Job title or designation. This value will be displayed in the Staff tab for a particular user but cannot be seen elsewhere within the platform.
Example: “Assistant VP of Enrollment” | Optional |
| List of schools with which the user is affiliated. This value can facilitate permissions assignments in the platform. This value must match a value supplied in the id column of the Schools tab of the configuration sheet (a foreign key to this column).
Example: “scs”, “cfa”, “cse” | Optional |
| List of departments with which the user is affiliated. This value can facilitate permissions assignments in the platform. This value must match a value supplied in the id column of the Departments tab of the configuration sheet (a foreign key to this column)
Example: “hci”, “arch” | Optional |
| For institutions using group-based feed management. The unique names of groups to which this user is assigned. Stellic matches on this string. This value must first be defined in either the group_permissions_student or group_permissions_other feed. Multiple values should be pipe-delimited.
Examples: “Primary Campus Advisors,” “Associate Deans” | required if applicable |