Skip to main content
Scrive logoeID Hub Documentation

Organisation ID (OrgID)

OrgID is a separate identity inside the same Freja app that represents the user as a member of their organisation, based on attributes the organisation chooses rather than their personal details. The private and work identities stay completely separate. To run a transaction against OrgID rather than the user's private identity, enable the OrgID service on the request.

For a user to authenticate or sign with OrgID, three things have to be in place:

  1. The user has a Freja eID+ account.
  2. The organisation has a user-management system, usually an IAM such as Azure, that grants the user the right to act on the organisation's behalf.
  3. A provisioning service tells Freja which user represents which organisation, and which attributes to share.

Once OrgID has been issued, the authentication and signing experience is identical to private Freja: the user simply chooses which identity to use at the point of authentication, when OrgID has been offered as an option. Attributes are shared only with the user's explicit consent, and Freja verifies them through its vetting process.

FrejaChoose identityto continue to your servicePrivatePersonal identityOrgIDScrive ABSame app, same flowOne sign-in, two identitiesWhen OrgID is offered as an option, the userpicks which Freja identity to present. Theauthentication flow is identical either way.Personal Freja identityname, date of birth, personal numberOrgID, the work identityattributes set by the organisationkept separate from the private identity

When the OrgID service is enabled, the completion data adds the organisation's OrgID fields: the issuing organisation's code and localised name, the user's identifier within that organisation, and any additional attributes the organisation provisioned. These fields are present only when OrgID is used.