FAQ

Organizations and accounts

What is the difference between my Eddy account and an Organization? Your account is your personal identity on Eddy. An Organization contains workspaces, Members, Maps and Sessions. Maps only exist inside an Organization workspace. See Organizations.

Who is responsible when our team collects personal data in a Session? Your Organization is the controller for data your Maps collect. Eddy Works processes that data for you. Plain-language summary: Policies. Full text: Trust Center.

How do Organization roles differ from roles on a Map? Organization roles control the workspace. Map Roles control who can act in a Session. See Permissions.

Do Guests need an Eddy account? Yes. A Guest signs in or creates an account before taking part in a Session. They do not need to become an Organization Member. See Membership.

Building Maps

Where do I learn the Map Builder? Start with Building — first Map tutorial, then stages, roles, and blocks.

What is the difference between a Map and a Session? A Map defines the stages, rules, Map Roles and blocks. A Session is one live run of that Map with its own participants and data. See Core Concepts.

Can I preview a Map before publishing it? Yes. Open Start in the builder and select Preview, or use the eye icon on a stage. Preview works while the Map is still a draft. See Your First Map.

Running Sessions

Why is my Session stuck? A common cause is a stage assigned to a Map Role with nobody in it. A session admin can use Assign Roles to fill the role. Depending on the situation, they can also nudge an assignee or mark the stage complete. See Blocked handovers and Managing Sessions.

What is the difference between Rewind and Reopen Stage? Rewind moves the Session back and deactivates the current stage. Reopen Stage opens a completed stage for correction without deactivating later stages. See Stage actions.

How do I see where Sessions are waiting? Open Operator. It shows how many Sessions sit at each stage and how long they have been there.

Data

Where do answers go after a Session? Answers from input and choice blocks are stored in sheet columns. A completed Session produces a main row, while per-participant stages can add rows to their own sheets. See Sheets.

Configuration troubleshooting

Use this section when the builder reports validation errors, a Session will not progress, or a block or sheet setup does not behave as expected. Open the red triangle in the builder toolbar for the full error list. See Validation and publishing.

Publishing and stage structure

Why can't I publish my Map? Every validation error must be resolved before you can publish. Warnings do not block publishing. Click the error count in the toolbar, fix each listed issue, then change the Map from Draft to Published. See Maps.

Why does validation say the Map needs a start or end stage? A Map with more than one stage needs one stage marked as the start. Every Map needs at least one end stage. Open the stage settings and use Set as start or Set as end. A stage with no outgoing transitions must be an end stage. See Your First Map.

Why does a stage say it has no sections or no blocks? Every stage needs at least one section and every section that collects or edits data needs at least one block. Add a section from the stage, then add blocks into it. Empty sheet sections used for view-only tables are allowed when add and edit are both off.

Why does a stage say it has no roles assigned? Select the stage and assign at least one Map Role in the stage settings. Without a role, nobody can open that stage in a Session. See Roles.

Why does a stage say no role can progress? At least one role on a non-end stage must have Can progress on. If every role is observer-only, nobody can complete the stage. Turn Can progress on for the role that should advance the Map. See Stage permissions.

Roles, start links and handovers

Someone opened a start link and cannot begin. Why? The self-service user must be assigned to a Map Role that includes the Map's starting stage. On the start link, set Self-service user to that start-stage role. See Self-service start links.

The next stage activated but nobody can work on it. Why? That is a blocked handover: the stage's Map Role has nobody assigned. A session admin should open Assign Roles and fill the role. Require assignments for all roles on start links to prevent this. See Blocked handovers.

Why can a participant see a stage but not edit or complete it? Check the role's stage permissions. Can write controls editing; Can progress controls completion. An observer has both off. An editor without completion can write but not advance. See Stage permissions.

Why won't a required discussion or poll let the stage finish? Discussions and polls need a session admin role on that stage. A session admin must complete the discussion (with an outcome) or close the poll before the stage can progress when the block is required. Enable Session admin on a Map Role assigned to the stage. See Discussion Block and Poll Block.

Transitions and policies

Why did the Session stop even though the stage was completed? If every outgoing transition has a condition and none of the conditions pass, the Map stops. Cover all expected cases or add a fallback transition with no condition. See Transitions.

Why is the next stage waiting after I completed mine? Either the target uses an All predecessors start policy and other branches are still open, or the stage has a time lock that has not fired yet. You will see Complete and Wait in those cases. See Start Policies and Activation Timing.

Why does validation warn about my start policy? Start policies only matter at merge points. A policy with no incoming transitions has no effect. A policy with only one predecessor behaves like Any predecessor. An All predecessors policy with conditional incoming transitions can wait forever if a condition never passes. See Start Policies.

Why is the stage still open after I marked myself done? The stage uses an All or Threshold completion policy. Your part is saved; the stage waits until enough assignees with Can progress finish. Read-only roles do not count. See Completion Policies.

I set a time lock. Why did the stage activate early or late? If the scheduled time has already passed when the predecessor completes, the stage activates immediately. Activation checks run about once a minute, so the stage may unlock up to a minute after the scheduled time. Start stages cannot use time locks. See Activation Timing.

Sheets, blocks, and bindings

Why does a block say it has no sheet or column binding? Input and choice blocks must bind to a sheet column. Open the block configuration, choose a sheet and column (or create a new column), then save. See Configuring Blocks.

Why can't my sheet section use the Map's default sheet? If Users can add new records is on, the section needs its own sheet. Adding rows on the Map default sheet would conflict with the Session's primary row. Use a dedicated sheet, or turn add off and keep the section view- or edit-only. See Sheet Sections.

Why can't a regular block use the same sheet as a sheet section? If a sheet section can add records on a sheet, other stages must not bind ordinary input blocks to that same sheet. New section rows would conflict with the Session's primary row. Put form fields inside the sheet section, or use a different sheet for stage-level blocks.

Why is my sheet section table empty or missing columns? Configure viewable columns on the sheet section. An empty viewable-columns list produces an empty table. Columns used by form fields should appear in the viewable list; add missing ones with the column picker. See Sheet Sections.

Why don't data-sourced options appear, or why can't I use them in transition rules? Source data must be filled on a previous stage. Options are snapshotted when the consuming stage begins. Transition rules on data-sourced columns cannot reference specific option values — use conditions like "is not empty" instead. See Data-Sourced Options.

Per-participant stages

Why won't validation accept my per-participant stage? Each per-participant stage needs its own dedicated sheet (not the Map default sheet and not shared with another per-participant stage). It also needs a completion policy of All or Threshold, not Any. Polls and discussions are not allowed on these stages. See Per-Participant Stages.

Why did switching to per-participant archive my blocks? Changing a stage between Shared and Per-participant rebinds data to a different sheet. Existing blocks are archived so they do not keep the old binding. Re-add the blocks after the switch. See Per-Participant Stages.

Why can't a shared stage use a per-participant sheet? Per-participant sheets belong to their stage's private rows. Shared stages must use the Map default sheet or another shared sheet. Bind shared-stage blocks to a non-per-participant sheet.