Altinn App Integration
How to get started sending notifications from an Altinn App.
1. Create and configure your Altinn App
Start by creating and configuring your Altinn App using Altinn Studio and your preferred code editor. Ensure that your app uses version 8.1.0 or higher of the NuGet packages to enable native notifications. For optimal performance and security, always use the latest stable version.
For detailed guidance on Altinn App development, refer to the Altinn Studio documentation.
2. Review policies for relevant resources in the 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 →
resourceIdhas 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:
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.
See Address Lookup for additional details on how address lookup works. ↩︎
For Altinn Apps, you must also ensure that the access-subject has
readgranted for all relevant tasks and events. ↩︎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. ↩︎
3. Understand 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.
4. Set up your app to send notifications
Follow the instructions in the Altinn App reference documentation to configure your app for sending notifications.