Overview
At the start of implementation, the project team users will be created in the SS&E instance--this will generally be around 5-10 users and should include IT team members such as SSO admin, data lead (including third-party vendor teams), email/calendar admin, LMS admin, etc. This allows the team members to have person records in SS&E, sign into the platform, and access the SS&E Admin screens.
These users will be given the Administrator role in SS&E. The roles can be changed at any time.
Person Data
The Project Manager will share a template for the institution to fill in with the person data for the users, which will follow the format below. Id, firstName, and lastName are all required. Must have at least one of username or emailAddress to enable SSO.
The Data Lead and Lead Admin should work together to fill this out, ensuring that the correct ID values are used.
| Column | Name | Notes |
|---|---|---|
| 0 | id | IMPORTANT: This must be the same id as what will be used for all student/staff/faculty ids in the person imports for data integration. Usually the database ID, SIS ID, student ID, employee ID, etc. This should include leading 0s if applicable. |
| 1 | username | This could be an email address or institutional username/user ID. IMPORTANT: Authentication/SSO uses either username or emailAddress. One of these two fields must match the SSO user identifier. |
| 2 | firstName | The user's first name. |
| 3 | lastName | The user's last name. |
| 4 | emailAddress | Institutional email address. IMPORTANT: Authentication/SSO uses either username or emailAddress. One of these two fields must match the SSO user identifier. |