Test users

Test users are team-scoped accounts that sign in with a national ID and a password instead of a real electronic ID. They make it possible to demo your application, run automated tests, and submit it for app store review without provisioning a real Audkenni identity for every reviewer.

When to use them

• App store review. Apple and Google reviewers need credentials that work outside Iceland. A test user gets them through the login.
• Foreign contractors and stakeholders who don't hold an Icelandic electronic ID but need to use your application.
• End-to-end tests that need predictable, repeatable identities and full control over name, email, and delegation context.

Test users are not real Audkenni identities — the resulting tokens carry the test user's national ID and profile, but the audkenni_* claims describe the test user, not a vetted citizen.

Plan and application setup

Test users are gated at two levels:

1. Plan tier. Your team's plan must support test users. If it doesn't, the Test users tab in team settings shows an upgrade prompt instead of the user list.
2. Per application. Each application that should accept test-user logins must have Test user access enabled in its application settings. An application without it rejects every test-user session.

The two-level gate is intentional: you can have test users on the team without exposing them on a production-facing application.

Creating a test user

Open Settings → Test users in the developer portal and click Add user. Each test user needs:

• Name — the value released by the audkenni_name and name scopes.
• Password — required at sign-in; only shown to the user who creates the test user. Cannot be recovered, only reset.
• National ID — does not need to match a real kennitala. Kenni prepends 00 automatically so test national IDs cannot collide with real ones.
• Email (optional) — released as email, automatically marked as verified.
• Phone number (optional) — released as phone_number.
• Mock companies — any of Kenni's built-in test companies the user can delegate to. Useful for exercising the Company delegations flow without real registry data.

Test users are visible to everyone on the team and can be edited or deleted at any time.

Signing in as a test user

On the Kenni login screen, choose Auðkenni app as the authentication method and enter the test user's national ID, including the leading 00. Click Continue, then enter the password on the next screen. From there the flow proceeds exactly like a real Audkenni login — including delegation prompts, consent prompts, and any other interactions the application has configured.

Next steps