What's changed in Domandata.

Any question can now carry Skip Rules. Add a rule to skip over this question or specific answer options when criteria match, or skip to another block (including End of Survey blocks) when criteria match. Conditions can use earlier answers, flow variables, linked panel columns, or branch arms — so even the first question can be skipped from panel data. A skip-to redirect takes effect when the respondent advances past the page with the triggering question. Redirects appear on the Flow canvas as dashed connectors (distinct from quota connectors) that can be hidden and shown from the canvas controls or by right-clicking the canvas, and they are included in the exported flow diagram.

Custom survey themes are now generally available in Deploy → Theme for all workspaces, with the legacy HTML/CSS header fields removed. Themes can still be seeded from a public homepage URL: Domandata fetches the page server-side, imports the logo shown in the page header (including custom header components and logo containers such as PageLogo) instead of defaulting to generic site icons, extracts a five-color palette from that logo, matches detected web fonts (including fonts declared in linked stylesheets, Google Fonts links, and @font-face rules) to the theme font picker and loads them from Google Fonts in Deploy and Preview, infers the accent color from CSS tokens such as `--signal`, the first `--*accent*color*` custom property (for example `courseAccentColor` on BYU course sites), and button styles, infers rounded vs. square corners from design tokens like `--r-none` and linked stylesheets (defaulting to square corners when the site does not clearly use rounded UI), and leaves light/dark mode unlocked when the source site defines both themes (including `data-theme` light/dark pairs in linked stylesheets) or only locks to one scheme when the site clearly skews that way. Dual-theme imports now also store separate light and dark palettes so respondents actually see the correct colors in each mode. You can upload a logo in Deploy → Theme (one logo is used in both light and dark mode by default, with an option to use separate logos per mode); brand import tries to fetch both from the source site when they differ (including sites that invert a single logo with CSS such as `--logo-filter`) and derives a dark logo automatically when needed. The theme preview also includes a color-scheme dropdown beside the question-type preview when light and dark modes are unlocked; when a theme is locked to light or dark, that preview toggle is hidden. Alternating row shading now uses each theme's secondary background color so it stays visible in dark mode as well as light. Color swatches in the custom theme builder also fill their rounded picker buttons correctly, and pasting a hex value that already includes # no longer duplicates the leading hash. Short custom-theme survey pages no longer leave a large empty band below the questions and navigation buttons.

Export now includes a Citation and Replication section for OSF, Harvard Dataverse, and Zenodo. Deposit either the survey instrument (for methods citations) or the full replication package (with response data), then copy APA, methods, BibTeX, and persistent-identifier snippets once a deposit exists. GitHub Sync has also moved here from Deploy, below Citation and Replication.

Institutions with a designated admin get an Admin tab: upload a logo (up to 2.5 MB) that appears next to the Domandata wordmark for every member, with an option to use separate light and dark logos; manage Standard and Pro seat pools separately, excluding members who pay for their own plan; search members, assign institution plans, promote or demote admins, or remove members (not yourself or the last admin); curate a shared institution library visible to every member; set an institution-wide default survey template; and optionally require institution members' surveys to use the institution logo. That logo now also appears in the survey editor header, and Admin and Classroom appear in the survey editor overflow menu in the same order as the full header.

Unfinished responses can now be automatically submitted — when a participant closes the tab, after a configurable number of days from when they started, or both (on by default: tab close, and 2 days) — with the option to turn either off. A survey can also be given a close date, which submits every in-progress response and unpublishes the survey automatically. Both are configured from the Deploy tab's Data & Privacy settings.

A survey can be linked to a participant panel, and optionally to a prior wave of that panel's Study, from Survey Options. Once linked, a respondent's known panel attributes — and, if a prior wave is set, their real answers from that earlier wave — can be piped into question text with {{panel:field}} and used to stratify treatment assignment or quotas, the same way an in-survey variable or quota already can. A prior wave's answer wins over a same-named panel attribute.

An Advanced section under Settings → GitHub Sync lets you set default export options (CSV or JSON, labels vs. recode values, flattened JSON) and custom starter files with {{Creation Date}}, {{Survey Name}}, and {{Repo Name}} placeholders for every new survey repository. Disconnecting a repository or GitHub entirely now stops scheduled sync and revokes data access. Failed repository creation is cleaned up automatically, and new repos exclude free-text and identifying answers by default.

Settings → New Default Survey now lets you pick a saved template — a whole survey — as the starting point for every new survey you create, cloning its blocks, flow, and branching in full. Once a template is set, the survey-wide General options below it disappear, since the template's own settings apply instead. A Workspace specific default toggle restricts the template to one chosen workspace, and workspace owners can set it as that workspace's default for members who haven't picked their own.

A new Advanced section under Settings seeds defaults for the Deploy tab's response table and export options — recode values vs. display labels, splitting compound questions (including Text Highlighter tags as separate columns), heatmap coordinate format, answer language, rotated tables, whether preview and Silicon Sample responses are included, and answer/question ordering columns. These apply the first time you open each survey's Export tab; each survey can still override from there.

/api/v1/export now accepts format=sav, format=dta, and format=rdata (SPSS, Stata, and native R data with factor columns and variable labels; capped at 15,000 responses per call). Multi-select questions can export as 0/1 indicator columns per option (expand_multi_select_as_indicators). SPSS/Stata variable labels use full question wording, with value labels covering more question types. The hosted R helper's dd_factorize() also covers card sort, MaxDiff, and conjoint columns.

Signing in with ORCID now pre-fills the Choose a Username step with your ORCID display name when it is available, the same way Google sign-in already does.

Institutions can be connected to their own SAML identity provider, so members sign in with their institutional credentials instead of a separate Domandata password. Access is matched by verified email domain and replaces the previous ad hoc domain-grant list.

Leave threaded comments on an individual question or on a whole block to flag something for a collaborator without changing the survey. A new Commenter role lets you add reviewers who can read and annotate a survey without giving them editing access, and comment activity generates notifications so authors see new and resolved threads.

A dedicated Translator collaborator role can author side-by-side translations of survey content for each configured language without touching question logic. Right-to-left layout is now fully supported for Arabic, Hebrew, and Persian, including the respondent-facing runner.

A classroom's owning professor can add teaching assistants who can help manage assignments and review student submissions alongside them.

Repeat a block once per item in a respondent-specific list — for example, once per household member or once per product a respondent said they use. The current loop item can be piped into question text, looped responses are aggregated on export, and item order can be held constant across iterations instead of re-randomizing each pass.

Conjoint attribute-level combinations can now be stratified, or blocked, across respondents by a chosen variable, mirroring the stratified-blocking pattern already available for treatment assignment in Flow branching.

A public, token-gated Quota Status page shows live fill counts for a survey's quotas without requiring survey-editor access, and a new Vendor Links panel in Deploy generates per-vendor links to it — useful for giving panel providers visibility into their own traffic.

Quotas can be organized into named groups and reordered, can trigger a variable value when they fill, and a matrix generator can bulk-create every crossed combination of two or more quota dimensions at once. The response table also shows each response's completion status against the quota that routed it.

Surveys can be imported directly from Google Forms and Microsoft Forms exports, in addition to existing import formats. A Harvard Dataverse connection can also be configured from Settings to push response data to a linked Dataverse repository.

Record a named sequence of authoring actions — adding questions, setting options, and similar steps — as a macro, then re-run it against another block or survey instead of repeating the same setup by hand.

CAIQ and HECVAT security self-assessments are now available for procurement and security teams evaluating Domandata, alongside the existing Trust Center documentation.

When two people are editing the same survey at the same time, a banner now warns before one person's changes could silently overwrite the other's, instead of the later save quietly winning.

Query parameters appended to a survey link by a research panel (for example a Prolific PID or a CloudResearch/Cint ID) are now captured automatically and can be substituted back into the end-screen redirect URL, so respondents return to their panel with the right identifiers attached.

Randomization defaults were audited across the app for consistent even-vs-random behavior. Block-level randomization inside Flow branching was fixed, and randomized treatment assignment now balances within each stratum instead of only across the overall sample.

Recoded variables that combine multiple source questions into one interaction term now support three- and four-way interactions, not just two.

Survey editor element loading, export generation, and page-load speed (including Largest Contentful Paint) were optimized, alongside a pass of general accessibility improvements across the app.

An internal search index now powers finding surveys and help content faster and more consistently.

The app header and footer received a visual cleanup, including a corrected gradient and a copyright notice, along with updated social links.

Each citable release on /changelog links its Zenodo DOI when one exists, and points to /cite for copy-ready snippets. Pull requests that change product code must bump the product version and update src/lib/changelog/releases.ts unless they are docs/tests/CI-only or marked skip-changelog / skip-version.

When Track Link Clicks is on, each unique href in a question is stored and exported as its own 1/0 column (Ask3_link_1, Ask3_link_2, …) instead of a single comma-separated list of clicked URLs. Authors can rename those columns in question Options, including through the set_link_tracking_names MCP tool.

Fixed a bug where answer options anchored or locked to a fixed position (for example a trailing "Other" or "None of the above") could still shift position under randomization.

Fixed block drag-and-drop in the Block Builder, block reordering within conjoint permutation blocks, and several Flow canvas rendering issues.

Quotas are now hidden from the Flow canvas by default to reduce clutter, snap correctly when dragged, and read clearly in dark mode.

Fixed a bug where a Settings section could silently resave its stored values the moment it mounted, which could wipe out an edit that was still pending elsewhere on the page.

Fixed survey sharing and collaborator invites, a race condition in the survey search field, rich-text paste formatting, a toggle switch's hover state, a brief flash on survey load, and curly-brace literals rendering incorrectly in help articles.

Every authenticated-app URL that previously lived under /personal (settings, surveys, panels, classroom, account, and more) now lives under /workspace instead. This does not affect respondent-facing survey links (/s/…), but any bookmarked or previously shared /personal/… link into the app itself will no longer resolve — replace /personal with /workspace in any saved links.

Row-level-security policies and security-definer grants added for the Commenter and Translator roles, quota status links, and related features were reviewed and hardened, including an initplan performance fix and closing a couple of read-access edge cases uncovered during the review.

Short Answer questions can now validate a response as an email address, phone number, or US zip code, alongside the existing integer/number/contains/Python options. Phone number responses are auto-formatted as the respondent types, robustly handling a leading "+", spaces, dashes, and parentheses. By default a country-code dropdown (e.g. +1) sits next to the number field so respondents can pick their own country; this dropdown can be turned off in favor of a single field, with a further choice of whether the respondent must type their own country code or the number is assumed domestic to a configured default country.

Auto-Tidy automatically collapses unfocused blocks in the Block Builder as you work, keeping the canvas clean without requiring manual minimisation. Extreme mode and drag-to-expand options are configurable in Settings → Advanced.

Survey content can now be authored in multiple languages side-by-side using Translation Mode. Translations are attached to individual blocks and exported alongside primary content.

Failed sign-in attempts are now logged to the audit trail alongside successful logins. Account deletion is now fully self-serve from Settings → Account → Delete account, with confirmed deletion of all surveys and response data. Audit logging was extended to cover sign-outs, role changes, and account deletion events.

Panels let you define and manage named respondent groups for targeted distribution. Create a panel, attach it to a survey deployment, and track panel-specific response quotas — useful for longitudinal studies and follow-up waves.

The Chrome extension received stability improvements: a more reliable ACK-based handshake replaces the previous availability check, the service worker cache strategy was updated to reduce first-load cold starts, and edge cases around auth cookie handling in extension contexts were resolved.

The Domandata Offline Editor Chrome extension lets you continue editing surveys when you lose your internet connection — similar to offline editing in Google Docs. Changes are queued locally and synced back to domandata.net automatically when you reconnect. All cached content stays on your device and is never sent to third parties.

Resolved a bug where auto-suggest answer completions would fail silently on certain question types. Suggestions now surface more consistently across short-answer and multiple-choice questions.

The full application — Block Builder, Flow, Deploy, and Export — is now responsive and usable on mobile and tablet screens.

Every pull request now runs automated ESLint, TypeScript type checking, and an npm dependency security audit before merging. The main branch is protected: checks must pass and a peer reviewer must approve.

A dedicated Settings area with Account, Accessibility, and Advanced tabs. Account settings cover profile, login credentials, MFA, connected accounts, API keys, and team workspace management. Accessibility settings include theme (light/dark/system), text scale, high contrast, and reduced motion. Advanced settings configure Block Builder defaults and question type organisation.

Save reusable blocks — question batteries, consent text, screeners, demographic items, recurring end screens — to your personal Library or share them to a team Community. Duplicate a saved block into any survey without rebuilding it from scratch.

Free, Standard, Pro, and Beta Tester plan tiers are now available. Free covers drafting and preview; Standard, Pro, and Beta Tester are paid plans billed through Stripe.

Import surveys from other formats directly into the Block Builder. Imported content is mapped to Domandata question types automatically, with a review step before saving.

Silicon Sampling uses an AI model to simulate plausible respondent answers for a survey, letting you preview what a response dataset might look like before launching in the field. Useful for testing export formatting and data cleaning scripts.

Auto-suggest proposes answer option completions as you write multiple-choice and scale items. Suggestions draw on common academic survey question wording and can be accepted, edited, or ignored.

Invite collaborators to individual surveys as Editors or Viewers. Team workspace members inherit team-level access; survey collaborators see only the surveys they have been explicitly invited to.

Attach response quotas to any Flow ending or treatment arm. When a quota is filled, new respondents matching that path are routed to a designated over-quota ending. Quotas are exported with the response data.

View, filter, and delete individual or batch responses from within the survey. Responses can be filtered by completion status, date, and Flow path. Bulk delete is confirmed before execution.

Each live survey link now generates a QR code suitable for print materials, posters, and classroom distribution.

Surveys can include an invisible reCAPTCHA challenge to reduce bot submissions. The reCAPTCHA score is recorded with each response for post-hoc filtering.

Compose survey instruments in clearly separated question blocks. Supported question types at launch: multiple choice, dropdown, short answer, ranking, Likert grid/battery, slider, conjoint, heatmap, content block, and Text Chat. Questions within a block can be reordered by drag-and-drop, and response order can be randomised.

Model your entire respondent path visually. Connect blocks with eligibility screeners, random assignment nodes, treatment arms, and quota-based endings. The Flow diagram is exportable and can be attached to methods documentation.

Publish a survey version to a live respondent link. Preview mode lets you walk through every path before launch. Multiple versions can be managed independently.

Download response data with variable names, recoded values, assigned treatment conditions, randomised field orders, and completion metadata intact — ready for direct analysis in R, Python, or Stata without manual cleaning.

Sign in with an institutional Google account or your ORCID identifier. Email-and-password accounts are also supported.

Apply a visual theme to the respondent-facing survey. Themes control typography, colour, and layout of the live survey link.