Core Concepts
Understanding the following building blocks will help you get the most out of ResponseDock.
Workspace
A workspace is an isolated organizational unit — it owns surveys, members, branding, API keys, and webhooks. A user can belong to multiple workspaces with different roles in each.
Survey
A survey is the top-level entity. It has a title, slug, status, and a list of versions. The active version is what respondents see.
Survey Statuses
| Status | Meaning |
|---|---|
draft | Being edited; not yet published |
scheduled | Published but start date is in the future |
online | Live and accepting responses |
paused | Temporarily not accepting responses |
closed | Responses permanently closed |
archived | Hidden from default lists |
Survey Version
Every published change creates a new version. Responses are always linked to the exact version that was answered, ensuring historical data stays consistent. Draft edits are free before the first publish.
Pages
A survey is divided into pages. Respondents see one page at a time. Pages can be marked optional (skippable by the respondent) and can be drag-reordered in the builder.
Blocks
Each page contains ordered blocks. Block types include:
- question — any supported question type
- heading — section header text
- text — descriptive paragraph
- divider — visual separator
- image — presentation-only image that does not collect an answer
- follow-up email — optional email consent collection block
Question Types
| Type | Description |
|---|---|
radio | Single-choice from a list |
checkbox | Multiple-choice from a list |
short_text | Single-line text input |
long_text | Multi-line textarea |
phone | International phone input with country flag and calling prefix |
country | Country dropdown with flag and country name |
date | Calendar day picked with the device's native date picker (optionally with a time of day) |
integer | Whole-number input |
decimal | Decimal-number input |
number | Legacy decimal input retained for existing surveys |
rating | 1–5 or 1–10 star/scale rating |
nps | 0–10 Net Promoter Score |
yes_no | Binary yes/no choice |
dropdown | Select from a dropdown menu |
file_upload | Validated photo, document, or general file upload |
html_content | Sanitized rich presentation content |
Survey authors can mark any question as confidential. Respondents cannot change that setting, and only the survey's original author can access the protected answer or uploaded files.
Response
A response is a single submission from a respondent. It stores the survey version, answers, source tracking data, and optionally a respondent identifier if the survey is non-anonymous.
Trigger
A trigger links an SDK event (e.g., match_completed) to a survey. When the SDK fires an event that matches a trigger rule, the platform returns eligible surveys. The SDK then shows the survey at the appropriate time.
Webhook
A webhook sends an HTTP POST to a URL you configure whenever a survey event occurs (e.g., response submitted). Delivery is retried automatically with exponential back-off.
API Key
API keys authenticate SDK and programmatic API access. They are scoped to a workspace and can be revoked at any time.
Member Roles
| Role | Scope | Permissions |
|---|---|---|
| Super Admin | Platform | Full platform access |
| Workspace Owner | Workspace | Billing, members, settings, surveys, branding |
| Workspace Admin | Workspace | Surveys, analytics, integrations, branding |
| Editor | Workspace | Create / edit surveys |
| Viewer | Workspace | View analytics only |