Effectory's technical requirements

At Effectory, we are dedicated to helping organizations utilize our services to their fullest potential. In this comprehensive guide, we provide detailed information on the technical requirements necessary for seamless integration and optimal performance. In this article, you will find:


Using Effectory’s services in the best way possible

At Effectory, we facilitate organizations in retrieving employee feedback through our tools and services. To ensure smooth operation, it is crucial that organizations meet our technical requirements.

When a survey starts, we send e-mail invitations to all participants, containing a hyperlink to access the questionnaire. Similarly, when the survey results are made available, we invite coordinators and respondents to view them through our online dashboard.

The settings below are crucial to guarantee that these e-mails are delivered smoothly and that our online environments can be accessed as intended. 


Prevent these common issues first

  • Ensure rate limiters are set to at least 300.
  • Set connection limits to a minimum of 40.
  • Turn off spam filters for Effectory emails.
  • Implement denial of service prevention measures.
  • Web content filtering for the resources used in the survey.
  • Consider filters like Microsoft Outlook Focused Inbox or Google tabbed Mailbox.
  • Address grey listing issues.

If you have any questions, feel free to contact your Customer Success Manager or our Helpdesk via helpdesk@effectory.com.


Whitelisting our servers

To facilitate smooth communication during survey periods, it's essential to whitelist our servers to receive emails correctly. We provide detailed requirements based on e-mail address, FQDN e-mail server, and IP e-mail server.

Based on e-mail address: Based on FQDN e-mail server: Based on IP e-mail server:
@effectory.nl mail4.effectory.nl
@effectory.com bnc3.effectory.com


Using accessible web servers for our tools

Access to our web servers is vital for using our tools effectively. This section outlines the accessibility status of various web servers and any additional requirements for optimal functionality.



These web servers are accessible and can be used without any problems.

Additional requirements

These web servers are accessible but have additional requirements. Please make sure the following settings are enabled for these web servers:

  • Local storage
  • Third-party cookies
  • Add the web server as trusted site

Note that we cannot check if you configured the settings above correctly.

Not accessible These web servers are not accessible. Make sure these web servers become accessible, for example by making sure no firewalls are blocking them. If you do not do so, you may not be able to use a specific application.


Web servers
Additional requirements https://survey.effectory.com Additional requirements https://login.effectory.com
Additional requirements https://myfeedback.effectory.com Accessible https://questionnaire-webapi.effectory.com
Accessible https://ecestore.effectory.com Additional requirements https://my-reporting.effectory.com
Accessible https://reporting-webapi.effectory.com Additional requirements https://signin.effectory.com
Additional requirements https://my.effectory.com Accessible https://az416426.vo.msecnd.net
Accessible https://dc.services.visualstudio.com Additional requirements https://widget.effectory.com
Additional requirements https://participant-exchange.service.signalr.net Additional requirements https://myeffectory-project.service.signalr.net
Additional requirements https://results.service.signalr.net Accessible https://coremailings.blob.core.windows.net


Web servers specifically used for InternetSpiegel
Additional requirements https://internetspiegel.survey.effectory.com Additional requirements https://login.internetspiegel.effectory.com
Additional requirements https://myfeedback.internetspiegel.effectory.com Additional requirements https://my-reporting-internetspiegel.effectory.com
Additional requirements https://my.internetspiegel.effectory.com    


Single Sign-On

We support and recommend the use of Single Sign-On to securely access our systems. This section provides general requirements for SSO and specific instructions for integration with Azure Active Directory/Microsoft Entra ID, OpenID Connect, SURFconext, and ADFS.


General requirements for Single Sign-On

To be able to use Single Sign-On without issues, we need specific data delivered to us. Please make sure to deliver the User Principal Name (UPN)  to us when being asked for employee data.


SSO with Azure Active Directory/Microsoft Entra ID

Follow these steps if you're using Azure AD/Microsoft Entra ID.


SSO with OpenID Connect

If you use an OpenID Connect protocol, please send the requirements listed below to  helpdesk@effectory.com and then proceed to configure a client for Effectory in your identity provider.

When setting up the configuration in your identity provider, take into account the following:

  • Effectory supports the implicit and the authorization code flow in OpenID Connect.
  • A claim with the name “email” is required for authentication. The claims “given_name” and “family_name” are not required, but it would be preferable if they were also included in the token.
  • Two scopes will be used to get the required information: ‘openid’ and ‘profile’.
  • The callback URL used will be https://signin.effectory.com/openid/[identifier]/callback, where [identifier] is the identifier described below.

We recommend to arrange a test account so that Effectory’s development team can test the SSO implementation before enabling it for everyone.


OpenID Connect SSO requirements

To set up the configuration required, the following needs to be provided to Effectory:

  1. An identifier  for your identity provider, to be used by Effectory. A unique identifier is required to discern between different identity providers. This identifier will then be used in the login URL (https://signin.effectory.com/identifier) and in the callback URL.
  2. Provide your unique identifier using only alphanumeric characters, and no special characters or diacritics.
  3. The list of domain names that are used in your provider. Please provide a comma-separated list of domains, e.g.: @example.com,@domain.com,@company.com. It is currently not possible to use private e-mail address like Gmail.
  4. The e-mail address of the technical contact, that can be contacted in case of questions or issues.
  5. Share the OpenID well-known endpoint. This is your authority URL followed by ‘/.well-known/openid configuration’, e.g. https://login.domain.com/.well-known/openid-configuration.
  6. Share your ClientId, a unique ID in your identity provider that allows Effectory to communicate with it and authenticate.
  7. If you are using authorization code, provide the client secret generated by your identity provider. Make sure not to share this via e-mail. Instead, upload it to a secure location like My Effectory.


SSO with SURFconext

Effectory supports SSO with SURFconext. If your organization uses SURFconext, send an email to helpdesk@effectory.com and ask for a SURFconext integration. Make sure that you provide the following information:

  1. Your organization's name as known by SURFconext. Alternatively, you can look up your organization in the SURFconext metadata and provide us with the EntityID.
  2. The list of domain names that are used in your provider. Please provide a comma-separated list of domains, e.g.: @example.com,@domain.com,@company.com. It is currently not possible to use private e-mail address like Gmail.
  3. The e-mail address of the technical contact, that can be contacted in case of questions or issues.

Once we have received the necessary information, we will arrange together with SURFconext that your organization can log in to Effectory's software.



ADFS starting from Windows Server 2016 (v4.0) is supported when you use the OpenID Connect protocol.


Unsupported systems and protocols for SSO

Unfortunately we cannot support all systems and protocols used for Single Sign-On. Effectory does not support the SAML protocol and does not support ADFS 3.0 or below.


Multi-Factor Authentication (MFA)

At Effectory, we prioritize security and encourage the use of Multi-Factor Authentication

If you'd like to enable MFA for your organization, get in touch with your contact person at Effectory. To learn more about using MFA with Effectory, download our whitepaper.

Please note that if you are using Single Sign-On, you will have to set up your own MFA and cannot use the Effectory protocol.


Employee data (HRIS) integrations

HRIS integration (or employee integration) is a strategic alternative designed to automate the process of importing employee data into our platform. For organizations with extensive employee data, this option offers numerous benefits:

  • Data exchanges are automated
  • It’s less (human) error prone
  • Your employee information will be up to date
  • You and your Customer Success Manager at Effectory will save time
  • It will enable continuous projects

You can either integrate your employee data through a file exchange or with AFAS.


Requirements and responsibilities


Download the documentation needed for an AFAS integration


Download the documentation needed for a file-based (SFTP) integration


Download the documentation needed for a Personio integration


Download the documentation needed for a SAP SuccessFactors integration


Supported browsers for accessing Effectory services



2 most recent major versions



2 most recent major versions


2 most recent major versions


latest and extended support release (ESR)


Mobile and tablet


2 most recent major versions


2 most recent major versions


2 most recent major versions


latest and extended support release (ESR)


Testing your environment

Ensure compatibility and functionality by testing your environment using our questionnaire demo environment, available in both Dutch and English:


Further support

For any assistance or clarifications regarding technical requirements, your Customer Success Manager and our Helpdesk are here to help. Reach out to us for personalized support and guidance!

Was this article helpful?
5 out of 11 found this helpful

We're sorry to hear that!

Please tell us why.
Have more questions? Submit a request



Please sign in to leave a comment.