Last modified: Sep 29, 2025

Service Owner System Integration

How to get started sending notifications from a Service Owner System

1. Get started as service owner in Altinn

To get started with Altinn Notifications, your enterprise must be registered as a service owner in Altinn. For a step-by-step guide, see the Get started with Altinn guide (Norwegian language only).

This step is only necessary for new enterprises that have not yet established themselves as service owners on the Altinn platform. If you are already an established service owner, you can proceed directly with the next steps to start using Altinn Notifications.

2. Register your Maskinporten Client with correct scopes

To use the Altinn Notifications API, you must have a Maskinporten client with the correct scope.

The scope altinn:serviceowner/notifications.create is required for clients to access the Notifications API.

All registered service owners have been delegated this scope by Digdir and should be able to find it in their list of scopes in Samarbeidsportalen.

For a guide on how to register a new Maskinporten integration in Samarbeidsportalen, please see Altinn Authorization

3. Review policy for relevant resources in Altinn Resource Registry

Associating a notification with a resource, through the use of the resourceId-attribute, results in the policy of said resource being used to identify the correct recipients of the notification. All intended recipients must be granted read through the policy of the resource.

About resources and who receives1 notifications:

  • Notifications to private individuals (national identity number), explicit email address or phone number → resourceId has no effect
  • Notifications to an organisation number:
    • The organisation’s statutory contact information (at enterprise level) is always used
    • Without a specified resourceId → only statutory contact information is used
    • With a resourceId → in addition to the statutory recipient, any person meeting all the below conditions is notified:
      • The person must have currently configured their “custom contact information” on the recipient-organsiation
      • The person must have read access to the resource through the resource’s policy 2
      • The person must not have opted out of receiving notifications for this service 3

About resources and policies

A resource in this case can be both an Altinn App or a resource (tjenesteeierressurs).

A new Altinn Resources can be registered in Altinn Studio or through an API. Please reference Altinn Resource Administration for instructions on how to create a new resource.

The policy for both Altinn Apps and other Altinn Resources can be managed in Altinn Studio. Please reference the Altinn Studio documentation on how to do this.

  1. See Address Lookup for additional details on how address lookup works. ↩︎

  2. For Altinn Apps, you must also ensure that the access-subject has read granted for all relevant tasks and events. ↩︎

  3. Users actively opt in to services, which means that services not opted into are considered opted out. This implies that if a user opted into an Altinn 2 service at some point, they have in practice opted out of all other services — including any re‑implementation in Altinn 3. All Altinn 2 resources (services) are carried over into Altinn 3, but the user has therefore often (without being aware of it) effectively chosen not to receive notifications for the new Altinn 3 resource. ↩︎

4. Familiarize yourself with the guidelines and best practices for sending notifications

To ensure effective communication, it is essential to strictly define what qualifies as a notification and avoid overwhelming users with too many messages.

Familiarize yourself with our guidelines to understand what notifications should and should not contain, promoting digital safety and preventing notification fatigue.

5. Integrate against the Notifications API

You are now ready to start integrating against the Notifications APIs, see the developer guides for next steps.