Policy Bulk Upload Guide

Last Updated: February 12, 2026

This guide explains how to add multiple policies at once using the CSV bulk upload feature in the Policies Module. We'll walk through how to download the CSV template, prepare the file, and upload it.

1. Access the Bulk Import Section

1. Log in to the web portal.

2. Select Policies from the left-hand menu.

3. Open the Bulk Import tab to begin the process.

2. Download the CSV Template

We strongly recommend using the provided CSV template to ensure correct formatting. Click the green “CSV Template” button to download the file.

If you encounter issues with the CSV template, you can use an Excel template. Just make sure to save it as a CSV UTF-8 (Comma or Semicolon delimited) (.csv) before uploading.

3. Prepare the CSV File

Open the downloaded template in Excel or another CSV-compatible editor.

Important note before you start:

• Do not remove the column headers (first row). Delete only the placeholder rows.

• If you upload a row with an existing Policy Number, all data in that row will overwrite the existing policy, including empty cells.

• Fields that support multiple values require line breaks within the same cell (not commas).

How to create a line break in Excel

Double-click the cell in which you want to insert a line break. Click the location inside the selected cell where you want to break the line. Press Alt+Enter (Windows) or Option+Enter (Mac) to insert the line break

CSV Columns Explained

Required Columns

• Policy Number: Must be at least 8 characters and must be unique per policy. Supports alphanumeric characters. Please note that uploading an existing Policy Number will overwrite the existing policy.

• Name: Name of the policy.

• Country: Two-letter country code using ISO 3166-1 alpha-2 format (e.g. SE, DE, US).

• Start Time: Date and time when the policy becomes active. Determines when users can start registering. Supported formats (ISO 8601):

  • YYYY-MM-DD

  • YYYY-MM-DDTHH:MM:SS+00:00

• End Time: Date and time when the policy expires. Determines when users will be logged out. Supported formats (ISO 8601):

  • YYYY-MM-DD

  • YYYY-MM-DDTHH:MM:SS+00:00

Optional Columns

• Groups: Refers to pre-configured client groups. Value must be a UUID. Multiple groups can be added using line breaks within the cell

• Description: Free-text field used for segmentation and filtering.

• URL: Metadata for the policy holder. Used to display an icon or visual reference in interfaces such as the Partner Dashboard.

• Email Domains: Supports both email domains and explicit email addresses. Domains must be entered without “@”. Multiple entries must be added using line breaks within the cell.

• Identity Provider ID: UUID of the Identity Provider the policy should be linked to.
  Must be pre-configured during setup.

• Maximum number of users: Defines the maximum number of users that can be registered under this policy. You can omit it — if you leave it empty, it will automatically be set to the default value, which is 1,000,000,000.

• Resource types: Specifies the resource category. This field must use one of the predefined options available in the web portal dropdown menu and must match the listed values exactly as shown below:

  • assistance-id-card Card

  • assistance-info

  • certificate

  • claims

  • url

• Resource Titles, Resource Descriptions and Resource Data: These fields define resources visible to app and web users (e.g. ID cards, claims pages).

Resource Type Rules

The fields for Resource title, Resource Description and Resource Data are tightly linked. If one field contains multiple rows (line breaks), the other two must contain the same number of rows. Each row represents one resource.

The content required in the Resource Data field depends on the selected Resource Type:

• URL, Claims, and Certificate: The Resource Data field must contain a valid URL. These resource types link to external pages or documents that users access directly from the app.

• Assistance Information: The Resource Data field must contain text instructions.
  This text is displayed to the user in the app before they contact an assistance provider (for example, call instructions, required information, or important notes).

• ID Card: The Resource Data field must be left empty. ID Card resources are generated or handled internally and do not require a URL or text entry.

Make sure the content in the Resource Data field matches the selected Resource Type. Incorrect formatting may result in the resource not displaying correctly in the app.

4. Save and Upload the File

1. Once all data is entered, save or export the file as:
   CSV UTF-8 (Comma or Semicolon delimited) (.csv)

2. Return to the Bulk Import section.

3. Upload the file and complete the import.

If your file upload was successful, a green box will appear with the message “Your file import was successful.” If the file import failed you will see either a red or yellow box with the following messages:  

Your file import failed

Your file import failed because the file is not configured correctly. Reasons why your file import failed could be: 

Incorrect file format: The file that was uploaded isn’t a csv-file 

Misspelled headers: One or more column headers were misspelled. Please use our template. 

File formatting error: Your file is wrongly formatted. By default it should be formatted by comma separation (“,”) or semicolon separation (“;“).  

Ensure your file matches all of the criteria above and re-upload your file.  

Your file import failed

Your file import failed because something is wrong with the file content.  The row of the Policy that has triggered the error is indicated in the yellow box. 

Reasons why your file import failed could be: 

URL Is not a valid URL  

IdpId is not an UUID  

Ensure your file matches all of the criteria above and re-upload your file.