Get started with Breeze

Efficient onboarding

To ensure a quick and smooth onboarding in the Breeze portal, we have gathered some key points that will simplify the process for both you and us. Collect the necessary information according to the description below and send it in a single batch to your contact person at your Security Partner or Sotera.

It’s important to note that not all the information presented may be relevant to your specific project. We therefore recommend that you take the time to clarify any questions or uncertainties with your contact person before submitting the material.

This will greatly contribute to a more efficient and seamless onboarding in Breeze, ensuring that all involved parties are well-informed and aligned.

Before We Start

Signed agreements:
For the Breeze cloud service and card production, we require a signed Service Agreement, incl. an Data Processing Agreement (DPA).
Find out who will sign on behalf of your organization. Provide:

  • Signer’s name

  • Title

  • Email address

  • Mobile number

  • Your organization’s registration number

Contact information:
Main contact person and primary administrator (name, email, mobile).

Portal name:
The name of the portal(s) to be used. This does not have to match the company name and can be a location or department name if sub-portals are part of your solution.

Secure login:
Should 2FA (email code) be activated now or later?
Is Single Sign-On (SSO) relevant for your organization?

Project Details to Consider

To help us understand your project, review these points and share the scope with us:

Card design:
Number of card templates/designs to set up, such as:

  • ID card

  • Loan card

  • Visitor card

  • Parking card

  • Logo card, etc.

See card design requirements here [PDF LINK]: Logo and/or card design, 300 dpi, RGB, size 56.4 x 87.7 mm.

Personalization fields:
Which fields should appear on the card template? Entered by the requester or cardholder (via Duo ID)? Examples, and inform if they should be mandatory or not:

  • First name, Last name

  • Title

    • Would a preset drop-down list help with registration by avoiding unusual titles or misspellings?

  • Expiry date

    • Maximum Validity Period

      • Define the maximum duration (e.g., 3 years) for any card in your organization.

      • This ensures compliance and prevents indefinite access.

    • User-Controlled Shortening

      • Decide if the requester (or administrator) can set an expiry date shorter than the maximum allowed.

      • Example:

        • Max validity = 3 years

        • User sets expiry = 6 months for temporary staff

  • Location

    • Would a preset drop-down list help with registration by avoiding inconsistent spelling or variations in location names?

  • ID photo

    • Do you want a standard headshot, or should it include shoulders and upper body for a more modern card design?

    • The image size should match your preferred card design.

Import of personal data and ID photos:
If your project includes batch ordering of multiple records, we can import data from Excel or TXT files with structured data. You will receive a secure upload link—do not send data by email.
Check [PDF LINK] for setup and [Excel LINK] for sample data format.

Technology setup (RFID or magnetic stripe coding):
Should cards include RFID technology such as EM, HID Prox, MIFARE DESFire, MIFARE Classic, or other access control technologies?
Should cards include a magnetic stripe?
If yes, we will address this separately to ensure correct format and may need to test existing technology.

Shipping addresses:
Which addresses should be visible during checkout?

  • Fixed addresses only (managed by Administrator)

  • User-managed addresses (select or add during checkout)

Shipping methods:

  • Trackable letter mail or small parcel

  • Business parcel

  • Service parcel

  • Express overnight

  • Courier

Depending on your location, we can choose different methods. For production in Norway: Greater Oslo, Asker, and Bærum we can provide courier delivery; other regions use Posten Bring services.

Security:
Should we activate 2FA (included as a standard service)? A 6-digit code is automatically sent to the user’s email for login verification. Is Single Sign-On (SSO) relevant for your organization

Approval function:
Should card templates be configured so that one or more templates—or all orders—require approval before production?
Approval in the same portal or via a separate approval portal by another user or resource in your organization.

Merge of orders:
If you have multiple users and administrators, the Merg order functionality could save the organization of shipment cost by sending card produced as a service ones or twice a week to a preset adresse.

After card production

Do your project want us to set up AMR functionality where card data and/or status is reported back?