Skip to main content
Student integration identifiers link a Kralis student to the identifier used by an external system. They are useful when a partner system does not use Kralis student IDs or when the partner’s records need to be matched to Kralis data. Kralis remains the source of truth for the student record. An identifier stores only the external reference and the partner-supplied name; it does not replace or update the Kralis student’s name or other details.

​
Managing identifiers

Authorized school administrators and deans can manage identifiers from: Manage student integration identifiers The page supports:
  • filtering by integration and academic year;
  • searching external IDs, external names, and Kralis student names;
  • creating and updating an identifier in the dialog;
  • selecting and removing identifiers in bulk; and
  • opening the form with a student or year already selected from an integration workflow.
This is an internal Kralis management tool, not a public partner endpoint. It is currently available to authorized school administrators and deans. Partner workflows such as ESMOE sync use the same records but apply their own matching and conflict rules before creating or replacing identifiers. Developers integrating with these records can use the complete Student Integration Identifiers GraphQL API reference, including queries, inputs, mutations, pagination, metadata, and replacement conflicts.

​
Identifier fields

​
Year behavior

The year field is optional:
  • A yearless identifier applies across academic years.
  • A year-specific identifier applies to one academic year.
  • When both exist, an integration request for that year prefers the year-specific identifier and falls back to the yearless identifier.
ESMOE registration numbers currently remain with students across academic years, so ESMOE sync creates yearless identifiers. The selected academic year is still used to load the correct Annual students during synchronization.

​
Scope and uniqueness

Identifiers are school-scoped. The same external ID cannot be assigned to two students for the same integration and scope. A student can have one yearless identifier for an integration and, where needed, separate year-specific identifiers. The identifier model is generic so future integrations can use the same relationship without changing the Kralis student record. When an integration needs to correct an existing assignment, replacement is explicit: the old external identifier is removed from its previous student before the new student receives it. This prevents one external registration number from remaining linked to multiple Kralis students. Updating an existing identifier without supplying new metadata preserves its existing metadata. Removing an identifier does not change the Kralis student or any academic record.