Skip to main content

New: SSO and Verification Methods

Ken Van Mechelen avatar
Written by Ken Van Mechelen
Updated this week

What are SSO and verification methods?

By default, users must confirm their email via a code to create an account. This manual verification can be a barrier to participation. With SSO (Single Sign-On) options like Google, Facebook, or Microsoft Entra, users can register and log in with a single click, making the process faster and more user-friendly.

For projects that require stronger identity verification, you can add:

  • Unique code verification for specific participants

  • National ID authentication systems (available in select countries)

Access to these features depends on your subscription plan.

Different SSO and verification methods

Google and Facebook login (free)

These options provide an easy, low-barrier login experience. When enabled:

  • Users can register or log in by clicking a single button.

  • Their email is automatically verified through the selected provider (Google or Facebook).

To enable these options, contact the Support team using the chat bubble in your platform.

Microsoft Entra login (with additional fees)

This is ideal if your organization already uses Microsoft accounts internally.

Options:

  • Add Microsoft Entra login to a public page for general use

  • Restrict it to a private URL visible only to your staff

To set it up, send the following to Support:

  • Directory (tenant) ID

  • Application (client) ID

  • Login mechanism name (e.g., “Sign up with city account”)

  • (Optional) Logo URL for the login button

Support will activate the login option for you.

Verifying users with unique codes

This method is useful when access must be restricted to a specific group (e.g., members of a neighborhood, students, or employees).

How it works:

  • Users enter a code during registration or when trying to access a restricted project.

  • If their code matches your list, their account becomes “verified.”

  • Anyone without a valid code can still register but won’t be able to access certain areas unless verified.

Setup steps:

  1. Generate or collect a list of unique codes (e.g., invitation codes, internal ID numbers).

  2. Contact Support to integrate this list into your platform.

  3. Create a smart group for verified users.

  4. Use this group to define who can view or contribute to specific projects.

National identity authentication systems

We support integration with several national systems for secure identity verification:

  • Belgium: CSAM (e-ID, itsme)

  • France: FranceConnect

  • Chile: COW

  • Denmark: NemID

Common use cases:

  • Limit participation to citizens of a specific country

  • Prevent users from creating multiple accounts

  • Ensure participants register using their real identity

Setup process:

  1. Contact Support at least 2–3 months in advance to plan the integration.

  2. Our team will work with you and national authorities to get the necessary permissions.

  3. Once configured, users will verify themselves via the national system when registering or attempting to interact with a restricted project.

We do not store or access national ID numbers. The national system handles all authentication.

We may receive basic information (like first name, last name, email) to populate the user’s profile, additional data like age or residence is not transferred.

After setup:

  • Create a smart group for verified users via national authentication.

  • Limit project visibility or participation based on this group.

In France, FranceConnect can also be used as an SSO method, users don’t need to create a new account on your platform.

When to use which method?

Method

Ideal for

Requirements

Google/Facebook SSO

Fast and simple sign-up

No setup required beyond Support request

Microsoft Entra SSO

Staff or internal login

Microsoft Tenant + App ID + Setup

Unique Code Verification

Closed groups or targeted participants

List of valid codes + smart group

National Authentication

Secure ID verification for citizens

Country-specific setup + early planning

Did this answer your question?