Skip to main content

Security: SSO, MFA and GDPR

Set up single sign-on (OIDC), enable two-factor authentication, protect sensitive data and understand our GDPR compliance.

F
Written by François Forest

Menu → Settings → Advanced settings

In short: Feedier offers single sign-on (SSO) based on the OIDC standard, two-factor authentication (MFA) for password logins, and attribute security to hide sensitive data. All data is hosted in Europe.

Who can manage security?

Role

Access

Admin

Full access

Editor, Viewer, Restricted Viewer

No access

Set up single sign-on (SSO)

Since summer 2026, SSO configuration is available on the SSO page, which centralizes all configurations.

Why set up SSO?

  • Centralized identity management: password policies, MFA and device trust are managed in your identity provider (Microsoft Entra, Okta, Google…).

  • Fewer risks from weak or reused passwords.

  • Immediate revocation of access when an employee leaves.

Feedier supports the OIDC standard, which every modern identity provider supports (learn more about OIDC).

Overview

Step

Where

What you do

1

Your identity provider

Create an OIDC application and get the base URL, Client ID and Client Secret.

2

Feedier (Admin)

Enable OIDC authentication and paste these values.

3 (optional)

Both

Advanced configuration: Client mode, access group, role and team provisioning.

Already have the base URL, Client ID and Client Secret from your provider? Skip straight to step 2.

Step 1: create the OIDC application in your provider (Microsoft Entra example)

This example uses Microsoft Entra. The steps are similar with other providers.

1.1 Register a new application

  1. Go to Applications → App registrations → New registration.

  2. Fill in the form:

    • Name: a clear name, for example "Feedier SSO".

    • Supported account types: depending on your needs, for example single tenant.

    • Redirect URI: select Web and paste the redirect URL shown in Feedier (see the box below).

  3. Click Register.

Where do I find the redirect URL? In Feedier, go to Advanced settings → Authentication and click Enable OIDC authentication: the redirect URL is displayed.

1.2 Configure authentication

  1. Open the Authentication tab of the registered application.

  2. Front-channel logout: leave this field empty.

  3. Under Implicit grant and hybrid flows, enable ID tokens.

1.3 Configure API permissions

  1. Go to API permissions → Add a permission.

  2. Select Microsoft Graph.

  3. Choose Delegated permissions.

  4. Add openid and email (in addition to User.Read, which is there by default).

Critical step: grant admin consent

After adding the permissions, click Grant admin consent for [your organization] above the list of permissions, then click Yes.

Without this, every user is blocked by an "Approval required" screen at login, even if the Feedier configuration is perfectly correct. All 3 permissions (email, openid, User.Read) must each show the Granted status.

This consent is given only once for the whole organization: no action is needed user by user.

1.4 Get the endpoints and the Client Secret

  1. From the application's Overview page, note the endpoints and the Client ID: you will need them in step 2.

  2. Go to Certificates & secrets and generate a Client Secret. Copy it right away: it won't be visible again.

Step 2: configure SSO in Feedier

  1. In Feedier, go to Advanced settings → Authentication.

  2. Enable OIDC authentication and choose the Server flow type.

  3. Enter the values you got in step 1:

    • Base URL

    • Client ID

    • Client Secret

  4. Save.

For Microsoft Entra (Azure), the base URL must end with /v2.0: https://login.microsoftonline.com/<tenant-id>/v2.0.

What happens when SSO is enabled

Enabling SSO is silent for users: no email or notification is sent.

Situation

Behavior

Users already logged in

They stay logged in: their session remains valid until it expires naturally or until they log out.

Next login

Feedier detects that the organization uses SSO and redirects the user to your identity provider. This is when SSO takes effect.

Notification

None. For an immediate switch (for example to confirm it works), let your users know and ask them to log out and back in.

Employee without a Feedier account

An account is created automatically with the Restricted Viewer role, with no manual action. An admin can then change it in the user settings.

Account matching

It is based on the email address: the address in your provider (Entra/Azure) must be identical to the one registered in Feedier for each user.

In summary: silent activation, with a natural switch at each user's next login.

Test and roll out

  • Click the Login URL shown in Advanced settings → Authentication: you should be redirected to your provider's authentication page.

  • Once SSO is enabled, logging in with a username and password is no longer allowed. Run your tests in a private window and keep an active session in your main window so you don't lock yourself out.

  • Share the Login URL with your users, ideally on your intranet. It is the most reliable route.

Why doesn't bx.feedier.com redirect to SSO right away?

Right after activation, a user who goes to bx.feedier.com and enters their work email may not be redirected immediately. This is expected:

Cause

Explanation

Solution

Browser or session cache

A tab opened before activation may display the old login page.

Close and reopen the tab, or use a private window.

Server-side cache

Domain detection (which matches an email domain to an SSO workspace) is cached. It refreshes within a few minutes to a few hours.

Wait, or use the Login URL.

Email not entered

The redirect triggers after the work email is entered. Without an email, there is no domain to recognize.

Enter the email before clicking "Log in".

Recommended during rollout: share the Login URL directly (in Advanced settings → Authentication). It bypasses domain detection and works immediately after activation.

Advanced configuration

MFA and password login

  • When SSO is enabled, password login is disabled: the only way in is the SSO Login URL.

  • If your identity provider already handles MFA, you can disable Feedier's MFA in Advanced settings (see Enable two-factor authentication).

Client mode (browser-side SSO only)

In Client mode, the Feedier server never communicates with your identity provider: the entire OIDC exchange happens directly in the user's browser. To enable it, choose the Client flow type in step 2.

Recommended if your identity provider sits behind an internal firewall or requires a VPN.

Best practice: manage access with an Entra group

By default, any user in your Azure tenant can authenticate through the Feedier SSO application. To restrict access and keep a clean, auditable list of Feedier users, create a dedicated Entra group:

  1. In Microsoft Entra, go to Groups → New group and create a security group (for example Feedier Users). Add every employee who needs access to Feedier.

  2. Go to Enterprise applications → Feedier SSO → Users and groups, click Add user/group and assign this group.

  3. In the Feedier SSO app registration, open Properties and set Assignment required to Yes. Only group members can then authenticate: everyone else is blocked by Entra before even reaching Feedier.

Benefits:

  • A single place to manage who accesses Feedier (add to or remove from the group).

  • Access revoked automatically when a user leaves the group or the company.

  • No user-by-user management in the Entra application.

  • Works with your existing HR or business groups.

If you turn on Assignment required after users have already logged in with SSO, only group members will be able to re-authenticate. First check that all your current Feedier users are in the group.

Automatic role provisioning

Instead of assigning roles manually in Feedier, provision them from your provider. This example uses Azure; the principle is the same elsewhere.

  1. In your Entra ID enterprise application, create the four app roles: Admin, Editor, Viewer, Restricted Viewer.

  2. Send your Workspace ID to [email protected]: our team completes the configuration on the Feedier side.

  3. Send a test link to a user to check.

Once role provisioning is enabled, only users with a provisioned role can access Feedier.

Automatic team provisioning

Map your groups to Feedier teams (marketing, subsidiary…): each user automatically lands in the right team.

  1. In Azure, create one group per Feedier team.

  2. In App registrations → Token configuration, add a group claim so that the group_id is included in the ID token.

  3. Send the group_id → Feedier team mapping table to [email protected]. The mapping is activated within 24 hours.

Example mapping:

group_id

Feedier team

fd7f72c6-cd68-4bad-b170-9aa2c1957128

Team A

9a48e151-e107-4555-a381-498174b947b9

Team B

With another provider (Okta, Google…), follow the equivalent steps: create the groups, configure the claims and include group_id in the ID token.

Enable two-factor authentication (MFA)

  1. Go to Settings → Advanced settings → Authentication.

  2. Turn on Enable multi-factor authentication.

MFA applies to every user who logs in with a password. With SSO, your identity provider handles MFA: you can disable Feedier's.

When a user changes their password, all their trusted devices are revoked and they are logged out. MFA is requested again at their next login.

Protect sensitive data

Attribute security makes an attribute inaccessible in filters, reports and exports.

  1. Go to Settings → Advanced settings → Attribute security.

  2. Under Attribute to make sensitive, select the attribute.

What changes

Details

Filters, reports, exports

The attribute is no longer accessible there.

API

The attribute remains visible.

Verbatims

Data detected automatically by AI (nlp_… attributes, such as a social security number) is anonymized in the text.

Irreversible action: an attribute made sensitive can't be restored.

Our GDPR compliance

Topic

Commitment

Hosting

In Europe, on AWS (Paris) for main production. On OVH for dedicated instances.

Feedier's role

Processor: you remain the owner of your data.

Backups

Daily and encrypted.

End of contract

Data is deleted automatically.

Access control

Roles, teams, SSO and MFA.

Organization

Staff trained on GDPR and ISO 27001, a data protection officer, an incident management procedure, independent penetration tests, customer audits available.

Feedier processes two types of personal data: respondent data (feedback content and attributes you send) and user data (for authentication). Users can view, edit or delete their data.

For any questions, contact our data protection officer: [email protected]. How AI is used is detailed in Ask Feedier and analyst agents.

Delete the workspace

In Settings → Advanced settings, Delete workspace erases all its data: feedback, sources, reports, users and settings.

All users lose access immediately. Deletion becomes permanent after 30 days; until then, an admin can restore the workspace.

FAQ

Can we enforce SSO for all users?

Yes. Once SSO is enabled, password login is no longer allowed. To limit access to a specific list of employees, use a dedicated Entra group.

A user enters their email on bx.feedier.com but isn't redirected. Why?

Browser cache, domain detection cache (a few minutes to a few hours) or email not entered. See the details above. The Login URL works immediately.

Users see "Approval required". What should I do?

Admin consent has not been granted in your identity provider. See step 1.3.

An employee logs in with SSO without a Feedier account. What happens?

Their account is created automatically with the Restricted Viewer role. An admin can then change their role. If role provisioning is enabled, the role assigned in your provider applies.

Our provider isn't Microsoft. What should we do?

The steps are equivalent with Okta, Google or any OIDC provider: create the application, get the base URL, Client ID and Client Secret, and, for team provisioning, include group_id in the token.

For any questions, contact [email protected] or your Feedier project manager.


Last reviewed: November 11, 2026, version 4.23.5.

Did this answer your question?