Agile Research 26ARCR3.1 release notes

Release starting 9 September 2026

Notice

Security policy updates for Medallia Agile Research

To further protect user accounts and client data in response to an evolving security landscape, Medallia is implementing enhanced security requirements for all Medallia Agile Research accounts. These changes include a transition to mandatory Multifactor Authentication (MFA).

Key dates and deadlines

  • November 4, 2026 (Extended Deadline): Mandatory MFA compliance goes into effect.

  • Post-Deadline Impact: If MFA has not been configured by November 4, 2026, users will automatically be redirected to the MFA setup wizard upon logging in and will be unable to access the platform until setup is complete.

Action required: How to enable MFA

MFA is currently available for users to enable on their profile page. To set up MFA:

  1. Download a mobile authenticator app, such as Google Authenticator or Okta Verify.

  2. Log in to Agile Research and navigate to Account > Profile.

  3. Under 2-step authentication, click "Turn On".

  4. Follow the prompt instructions to scan the QR code with your authenticator app and enter the verification code.

Single Sign-On (SSO) and Medallia Experience Cloud customers

  • Existing SSO users: Clients currently utilizing Single Sign-On (SSO) are unaffected and can continue using their current SSO implementation. No new SSO implementations will be allowed.

  • Medallia Experience Cloud (MEC) customers: If your users already access Agile Research via SSO through the MEC Application Switcher, no additional steps are necessary. If your users still rely on individual email/password logins, you have to switch to logging in through MEC. Account administrators can request a transition to MEC SSO access by submitting a support ticket via the Help section of their Agile Research account.

Support

For questions or support, visit the Medallia support portal at help.medallia.com.

Editing live surveys

All live surveys are now protected against structural edits by default. This change safeguards response data integrity and supports enterprise governance requirements with no configuration needed. See Editing live surveys for details.

Why we made this change

Uncontrolled structural edits to a live survey can affect in-progress responses, invalidate existing data, and introduce errors that are difficult to catch or reverse. This change brings Agile Research in line with standard enterprise safeguards for research platforms operating at scale.

What's changing

When a survey's status is Live, structural edits are blocked for all users, regardless of role or permissions. This includes:

  • Adding or removing questions

  • Changing question types

  • Marking questions as required or not required

  • Hiding or showing questions

  • Reordering pages

  • Modifying branching

  • Modifying page display logic

This behavior applies platform-wide and cannot be turned off at the account or survey level.

You can still open survey settings pages to review them while a survey is live, but Save will be grayed out to prevent changes.

What's not changing

Inline text edits are still fully supported on live surveys. You can continue to correct question text, answer choice labels, and page text without pausing or closing your survey. These edits don't affect survey structure or in-progress response data and won't trigger a status change.

Making structural changes to a live survey

To add questions, change logic, or make other structural edits, you'll need to:

  1. Pause or close the survey.

  2. Make your changes.

  3. Relaunch the survey.

The survey builder now visually reflects the read-only state while a survey is live, with a contextual message explaining how to make structural changes.

Relaunching a survey

When you relaunch a previously closed survey:

  • The survey returns to Live status and read-only enforcement resumes.

  • All existing survey links (email invitations, live links, and other distribution channels) remain valid and no new links are generated.

  • Contacts who already received an invitation are not re-invited.

  • Contacts with statuses of Invited or Partially responded at the time of closure can pick up where they left off using their original link.

  • Contacts who had already completed the survey keep their Responded status and are not prompted to retake it.

  • Contacts with status Included at the time of closure receive an invitation upon re-launch if the email channel is active.

Highlights

  • Added an optional PO / Reference column to the Draft Panels and Purchased Panels tables.

  • The account summary box will show up on home page with a resolution of 1200px and above.

Resolved issues

  • Resolved an issue where broken CSL in the FROM field resulted in email invitation failures.

  • Improved activity logs to include logs for Smart Report creation.

  • Resolved an issue where the Favicon feature was not working for migrated surveys.

  • Resolved an issue wherein sign-In codes were not working correctly for the Paper Distribution method.

  • Resolved an issue where users were not able to provide responses from web links and emails within the same browser.

  • Resolved an issue where clicking Save in the question editor with blank required fields redirected to a random tab instead of the Question tab.

  • Resolved an issue where the account admin was not able to delete accounts.

  • Resolved an issue where prefill with CSL was not working correctly in the new survey interface.

  • Resolved an issue where question display logic conditions were disappearing after saving when the Matrix Single Select question type was used.

  • Resolved an issue where full tool users were not getting updated to report viewer only users.

  • Resolved an issue where translations were missing for the Close button on the custom work message popup.

  • Resolved an issue where formatting options were overlapping on the Media window popup when adding images to the text/media question type from the survey editor.

  • Resolved an issue where the unsubscribe link was broken on the opt-out page.

  • Added validation for display logic so that users can configure to a maximum of 20.

  • Users can no longer create hidden questions that are marked as required.