Back to Help
Settings

Team Collaboration for Research Surveys

Coordinate team access, review links, shared materials, and publishing decisions without losing the study record.

Collaborate Around The Instrument

Research surveys often involve faculty, students, analysts, field partners, or lab staff. Domandata workspaces and shared materials help teams coordinate survey building, review, reuse, and publishing without losing track of the research instrument.

Before collaborators edit the same project, decide which workspace owns the survey, who can approve wording, who can change Flow, and who is allowed to push changes to the published version. That agreement prevents a small convenience edit from becoming an undocumented design change.

Recommended Collaboration Workflow

  1. Step 1: Agree on the instrument map. Align on blocks, measures, condition arms, quotas, and codebook conventions before building.

    Step 1: Agree on the instrument map

    Personal Dashboard

    Live dashboard surface from the app shell (ephemeral help scene).

    Surveys

    Untitled surveyLast Modified
    Policy attitudes pilotLast Modified

  2. Step 2: Use the right workspace. Open Settings to confirm team and workspace access for collaborators who need to build, review, export, or reuse materials.

    Step 2: Use the right workspace

    Top Navigation

    This is the same navigation component used in the app shell.

  3. Step 3: Build shared materials once. Use the Library for approved blocks, question batteries, consent language, themes, and repeated end screens.

    Step 3: Build shared materials once

    Top Navigation

    This is the same navigation component used in the app shell.

  4. Step 4: Share draft links for review. Use draft links during review instead of public collection links, and include notes about which paths reviewers should test.

    Step 4: Share draft links for review

    Block Builder
    Preview
    Deploy

    Deploy

    Configure publishing, links, quotas, and theme from the Deploy tab.

  5. Step 5: Assign final ownership. Decide who owns wording, Flow, quota, publish, and export decisions.

    Step 5: Assign final ownership

    Top Navigation

    This is the same navigation component used in the app shell.

  6. Step 6: Run a final pilot. Preview, publish-test, and export-test before live collection.

    Step 6: Run a final pilot

    Block Builder
    Preview
    Deploy

    Preview

    Walk through respondent-facing behavior in the same preview surface.

Protect Research Consistency

Assign one person to own final wording, Flow, and publish decisions. Avoid changing live answer labels, condition arms, quota definitions, or recodes without documenting the change for analysis.

  • Wording changes: note whether the change affects respondent meaning or only fixes spelling.
  • Flow changes: retest every affected path in Preview.
  • Quota changes: record the old target, new target, and response count at the time of change.
  • Export changes: tell analysts when variable names, recodes, or condition labels change.

Flow: Conditions and Routing

Block Builder
Preview
Deploy

Flow Canvas

Interactive routing surface from the app, running in no-persist help mode.

Consent and Study Intro

1 question

Political Knowledge Block

2 questions

Control Message

1 question

Treatment Message

1 question

Outcome Measures

2 questions

Survey Ends

Anchors explicit end of survey

Reusable Team Assets

Teams can standardize consent blocks, demographic batteries, screening blocks, themes, and validated scales through the Library. Save assets only after they have a clear owner, a descriptive name, and enough context for another teammate to know when the material is appropriate.

Block Builder: Add Block

Survey Editor

No-persist demo using the real builder shell.

Add a Block

Trash is empty.

Related Help