Education

IAM Core attributes

On this page

In order to use the education features, IAM Core must be populated with data from the school information system(s) you have through connectors. The connectors all come with pre made synchronization rules that will support the education features, but if you in case, here all required attributes:

Student -> Core Identity

Each student need to be created as an identity in IAM Core, with the below attributes:

AttributeDescriptionExample value
displayNameTo display human friendly in the user interfaceJohn Doe
entraObjectIdRequired by both student password and internet policy features in order to locate the Entra user account of the student09964771-f29e-48c5-9754-78bfa9e603e7
entraOnPremisesSyncEnabledRequired by the student password feature, if you need to use the AD Agenttrue
entraOnPremisesUserPrincipalNameDisplayed in the user interface, as the username of the studentjohn.doe@test.com

It is also recommended to populate these attributes:

  • nin
  • firstName
  • lastName
  • entraOnPremisesSamAccountName
  • dateOfBirth

Teacher -> Core Identity

Each teacher need to be created as an identity in IAM Core, usually connected with HR data as well, but that is techincally not a requirement. The below attributes are required:

AttributeDescriptionExample value
entraObjectIdRequired by the Universe Portal and API in order to map the Entra signed in session (JWT) to Core Identity09964771-f29e-48c5-9754-78bfa9e603e7

It is also recommended to populate these attributes:

  • nin
  • firstName
  • lastName
  • entraOnPremisesSamAccountName
  • dateOfBirth

Teacher and student relationship -> Core Relationship

The relationship between a teacher / student and the different educational groups they are member of are mapped as Core Relationships with the following attributes:

AttributeDescriptionExample value
identityA reference to the Core Identity of the teacher or student035e4651-afd6-4ddb-964f-405bc0e3fa89
orgUnitA reference to the Core OrgUnit for the education groupe6345196-084d-43d3-905f-19d3810a468b
typeAlways set to 'education' in order to tell the education services that this is an education relationshipeducation
subTypeAlways set to 'teacher' for teachers and 'student' for students, which tells the education services that the identity of this relationship is a teacher/student for the org unit of the relationship in questionteacher

There are also some optional attributes:

AttributeDescriptionExample value
startDateThe start date of the relationship, if ommited, the relationship is considered as having a start date in the past2026-08-01
endDateThe end date of the relationship, if ommited, the relationship is considered as having an end date in the future2026-08-01

OrgUnit

AttributeDescriptionExample value
displayNameThe name displayed in the Universe portal1st grade
parentA reference to the parent Core OrgUnit for the education group. See separate note on the org unit structure.d6052f2e-c130-4893-ac85-cbe2d2bb7e9b
typeAlways set to 'education' in order to tell the education services that this is an education org uniteducation
subTypeThe OneRoster type of the org unit. The values that have special uses are: schoolowner, school, ext:municipality, scheduled, ghost course and homeroom, but any other value may be usedteacher

Structure

In general, the following structure is used:

  • School owner or ext:muncipality
    • School
      • Scheduled
      • Homeroom
      • other types
Last updated 18 November 2026 Edit this page on GitHub
Esc