ID.me Verification Status in the Events Table
The Events Table captures changes when an applicant changes any field on their application. When a change occurs, SuperGlue will send a payload to the college to indicate there was a change made to a field.
The Event Type field will indicate what type of change was made:
UPDATE_PROFILE - a change was made to any of the fields.
FEDERATED_IDENTITY_LINK - a change was made that affects the ID.me verification status of the student.
Event Trigger for ID.me Status Changes
One of the features of the events table is the ability to capture an ID.me Status Change Event. The idme_status field will update when an applicant changes one of these fields:
first name
last name
address (address 1, address 2, city, state, postal code, country, and/or homeless status)
date of birth
Depending on if the student had previously been verified or not, the idme_status field will update to one of these states:
Previous ID.me Status ( | Current ID.me Status ( |
|---|---|
null or blank | verified |
unverified | verified |
verified | unverified |
When the event is triggered, the status is logged in the Events table and SuperGlue sends the data in the payload for the ID.me Verification Status Change Report.
ID.me Verification Status Change Report
When the ID.me Verification Status Change Report is enabled, colleges can get an email notification of the event, along with the student data for the account that triggered the event.
Verification status can be in one of these states:
The ID.me Verification Status Change Report runs one time per day, at midnight. When the report runs, it compares the current data to the report run in the previous day. If it finds that a student’s verification status has changed to verified or unverified, that student’s record will show on the change report. The student’s record will not show if the status changed to any of the other states (expired or staff_verified).
In the example below, student CAL5736 was in a verified state as of January 15 but on April 28, the status changed to unverified so a FEDERATED_IDENTITY_LINK event was triggered.
This workflow shows how idme_status = verified can change to idme_status = unverified:
The report may also show what changed to trigger the event. In this case, the last name was spelled differently on the last application and that field is included in the event payload:
{
"firstName": "Jane",
"previous_firstName": null,
"lastName": "CollegeStudent",
"previous_lastName": "CollegeStudddent",
"email": "janecollegestudent@domain.com",
"previous_email": "janecollegestudent@domain.com",
"cccid": "ABU9844",
"idme_status": "unverified",
"previous_idme_status": "verified",
"idme_confirmation_timestamp": null
}Notifications With Missing Fields
The date of birth and mailing address fields are not included in the ID.me Verification Status Change Report. This means that you may get a report indicating that there was a change to the ID.me verification status, but no data on what changed, because it was in one of those two fields. To see the date of birth and mailing address fields, look up the applicant using your Student Information System (Banner, PeopleSoft, Colleague) or the CCCApply Reporting System.
Key Fields
The Key fields in the Events table for ID.me notifications in the Events table are:
Field Name | Description |
| The three-digit college code (e.g., 111). |
| A unique identifier for each event. |
| The type of event (e.g., UPDATE_PROFILE' and 'FEDERATED_IDENTITY_LINK') |
| The detailed information for the event, which is often structured as a JSON object. |
| The timestamp when the event occurred. |
The misCode and eventId form the natural unique key for this table. For example, cases where sister colleges within a district share a single SIS, a single given eventId may be sent to both misCodes.
In addition to these core fields, the table includes other fields for tracking event processing in external systems (e.g., SIS-specific fields).
Field Name | Description |
| Identifier for the event in the college's SIS. |
| Timestamp of when the event was processed by the college's SIS system. |
| A flag indicating whether the event has been processed in the SIS. |
| Additional notes related to the event processing in the SIS. |
Note: The SIS-specific fields are not part of the core event payload, but are added to the records for the colleges' internal processing.
Description of fields:
firstName: The updated first name of the user. This field is a string with a maximum length of 100 characters.previous_firstName: The previous first name of the user, if applicable. This field is a string with a maximum length of 100 characters.lastName: The updated last name of the user. This field is a string with a maximum length of 100 characters.previous_lastName: The previous last name of the user, if applicable. This field is a string with a maximum length of 100 characters.email: The updated email address. This field is a string with a maximum length of 256 characters.previous_email: The previous email address, if applicable. This field is a string with a maximum length of 256 characters.cccid: A unique identifier for the user (e.g., CCCID). This field is a string with a maximum length of nine characters.idme_status: The current status of the user's ID verification (e.g., unverified, staff_verified, verified, expired).previous_idme_status: The previous ID verification status, if applicable. This field is a string with a maximum length of 50 characters.idme_confirmation_timestamp: Date with UTC time of when the ID verification was confirmed, if applicable.