Provisioning

Provisioning

This guide provides an overview of how to set up provisioning between Logins and Electa. It explains the purpose of provisioning, gives step-by-step setup instructions, and shows how new voters are created in Electa.

What Does Provisioning Do?

Provisioning is the process of automatically synchronizing voter data between Logins and Electa, streamlining voter management. With provisioning enabled, you no longer need to maintain two separate voter lists in each system. Instead, the voter list only needs to exist in Logins, and voters are only created in Electa after successful authentication through Logins.

Additionally, provisioning can be used with different authentication methods. With the feature “Authenticate by claim” (found under Configuration), it is possible to specify how the newly created voters must be authenticated (either by their national identification, their address, or their municipality).

  • This feature has been build for the Danish eID MitID and using this for any other type of election you should contact the Lumi Product Management team to assess whether the solution will work for your event type. Additionally, please note that using the Address and Municipalities claim methods only works in Denmark currently.


Setting up Provisioning

Before starting, configure the Login Hub as you normally would for your organization – see more information on that here. Ensure that the login method under “SSO Config” is appropriately configured towards your country’s authentication provider. For the examples shown in this guide, we use MitID as this is the Danish authentication provider.

Provisioning is configured under link groups using the link type ElectaLogins – ie. provisioning only works with links to Electa. These link groups correspond to voter groups in Electa.

When setting up a login link to Electa, enable the “Provision user” option. This will enable two other features: “Connector” and “Voter group”. Select the appropriate “Connector” and “Voter group” for the link. For more details on these features, see here.

Screenshot 2025-11-14 at 12.26.26.png

Once provisioning is set up in Logins, it can trigger a series of occurrences:

  • When a voter is successfully authenticated via Logins, their information is automatically stored in Electa.

  • The Logins' “Logins” log provides a history of which external IDs have resulted in new voter records in Electa.

Now, with the required configurations for provisioning set up, let’s take a look at how provisioning works with the different authentication methods.

Provisioning & authentication by national identification

Under Configuration of the Login Hub, start by setting up the authentication method as “national_id”.

Screenshot 2025-11-28 at 08.25.23.png

To successfully connect Electa and Logins, ensure that the correct national identification number is in the “External” field of your credential.

Screenshot 2025-11-28 at 09.11.00.png

Now, go to the Hub’s frontend. From here, proceed with authenticating yourself to access the election. Once you have successfully accessed the election, two things will happen:

  • A new voter is created in Electa

  • And in the “Logins” log of the Logins system, there is a new log corresponding to the new voter created in Electa.

Electa:

Screenshot 2025-11-28 at 09.45.37.png

Logins:

Screenshot 2025-11-28 at 09.46.44.png

 

Provisioning & authentication by address

Under Configuration of the Login Hub, start by setting up the authentication method as “address”.

Screenshot 2025-11-28 at 10.09.18.png

 

Now, under “Credentials”, enter the editing mode of the credential you wish to use. Fill in the field “Address” with your address, and save these changes. This will generate a code under “DAWA guid” – you will need to copy this code into the “External” field.

Screenshot 2025-11-28 at 10.10.53.png

Now, go to the Hub’s frontend. From here, proceed with authenticating yourself to access the election. Once you have successfully accessed the election, two things will happen:

  • A new voter is created in Electa

  • And in the “Logins” log of the Logins system, there is a new log corresponding to the new voter created in Electa.

Electa:

Screenshot 2025-11-28 at 10.13.10.png

Logins:

Screenshot 2025-11-28 at 10.13.35.png

 

Provisioning & authentication by municipality

Under Configuration of the Login Hub, start by setting up the authentication method as “municipality”.

Screenshot 2025-11-28 at 10.09.18.png

 

Go to the “Credentials” overview page. A new button “Manage municipalities” has appeared – click on it. In this municipalities' management page, you need to select all the necessary municipalities. This will create a credential with a code and name for each municipality.

Screenshot 2025-11-28 at 10.28.31.png
Screenshot 2025-11-28 at 10.32.13.png

 

Now, go to the Hub’s frontend. From here, proceed with authenticating yourself to access the election. Once you have successfully accessed the election, two things will happen:

  • A new voter is created in Electa

  • And in the “Logins” log of the Logins system, there is a new log corresponding to the new voter created in Electa.

Electa:

Screenshot 2025-11-28 at 10.35.45.png

 

Logins:

Screenshot 2025-11-28 at 10.36.27.png