1 min lukuaika
Aa register (NAV)
The Norwegian register of employment, read with a Maskinporten token supplied by the calling user.
Employment relationships from Norway’s national register — and the only integration in this catalogue where the user brings the credential, not the server.
What it is
Section titled “What it is”The Aa register (Aa-registeret) is Norway’s national record of employment relationships, run by NAV. This integration reaches it through a proxy API and looks up employment by employee, by employer, or by the party that reported it.
It does not hold a credential of its own. A real lookup requires a valid Maskinporten token from the calling user, which is what keeps access tied to a person and an organisation with the legal basis to make the query — rather than to a shared service identity that would flatten that distinction.
Use it for
Section titled “Use it for”- “Which employment relationships are registered for this employer?”
- “What is registered for this employee?”
- “What has this reporting party submitted?”
| Function | Answers |
|---|---|
| Usage guide | What a lookup requires, and how the token is supplied — the assistant reads this first |
| Find employment | Employment relationships by employee, employer or reporting party |
Two tools. The narrowness is the design: this is a register lookup, not an analytics surface.
Data and permissions
Section titled “Data and permissions”- The caller supplies the credential. A live lookup needs a valid Maskinporten token from the user making the request. Without it, there is no lookup.
- Read-only. Nothing is written to the register.
- Personal data. Employment records are about identified individuals, which is exactly why the access model is what it is.
Getting started
Section titled “Getting started”Your organisation needs a Maskinporten integration with the right scope, and the token has to reach the assistant at query time. Talk to your Customer Success Manager — this one needs a conversation about legal basis before it needs configuration.
Limitations
Section titled “Limitations”- Norway only.
- No token, no answer. This is not a degraded mode — it is a refusal, and it is deliberate.
- Personal data, with everything that follows. Having technical access is not the same as having a legal basis for a given lookup. That assessment is your organisation’s, and it belongs before the question, not after.
- Registry facts only. What was reported, by whom, for what period — not why, and not whether the reporting was correct.