Configure how your survey looks and behaves for respondents: colors, logo, progress bar, security, scheduling, and completion options.
Opening survey settings#
In the survey builder, open the Settings tab. The page is headed Survey Settings, and it is split into nine sub-tabs across the top:
| Sub-tab | What you set there |
|---|---|
| General | Title, description, internal reference, timezone, and the plugin build this survey uses |
| Scheduling | Survey status and the window the survey is open for |
| Responses | Partial responses, screen-out data, repeat submissions, anonymity |
| Experience | Welcome screen, progress bar, question numbers, page layout, respondent wording |
| Branding | Colors, logo, text sizes, custom CSS |
| Completion | Thank-you message, redirect, email summary |
| Security | Password, CAPTCHA, IP tracking |
| Sharing | Who else can open and edit this survey. See Collaboration |
| Quality Filters | Speeding, straight-lining and duplicate checks. See Quality Filters |
General#
Basic Information#
| Field | What it does |
|---|---|
| Survey Title | Required. The name respondents see and the name the survey is listed under |
| Description | A short description of the survey. A character counter sits under the box |
| Internal Name | A reference for your own team, such as Q4-2024-CSAT. Not visible to respondents |
Region#
Timezone records the timezone the survey is run in and is saved with the survey. The choices are Eastern Time (ET), Central Time (CT), Mountain Time (MT) and Pacific Time (PT). Base language is not set here; it lives in the Translations tab, covered in Multi-Language Surveys.
Plugin Bundle Version#
This one is unusual, so it is worth being clear about who it is for.
Some question types are built on custom interfaces that load their code from Intuify's content delivery network rather than from the survey app itself. Plugin Bundle Version decides which build of that code this one survey loads. It affects nothing else: ordinary question types, logic, quotas and exports do not go near it.
The first option in the list is Latest stable (default), and that is the correct choice for essentially every survey. Leave it selected and your survey always picks up the current stable build. Below it the panel lists up to ten registered builds, newest first, each showing its build id, its environment, the date it was deployed, and a latest tag on the newest one. Clicking one pins this survey to that exact build. A tick marks whichever option is active.
Only pin a build if someone at Intuify has asked you to, normally to reproduce a problem or to hold a live survey on a known-good build while a fix goes out. A pin freezes this survey on old plugin code: it will not pick up fixes, and nobody looking at the survey later will have any reason to suspect it. To undo a pin, click Latest stable (default) again.
Two things to know:
- The pin belongs to the survey, not to the account. Other surveys are unaffected.
- A pin set on a template is not carried over. Surveys created from that template resolve the current build as normal.
The section is hidden while you are editing a template, for that reason.
Sync from Cloudflare#
Sync from Cloudflare sits in the top right of the Plugin Bundle Version section, and it only appears if you are an Intuify platform administrator. Ordinary accounts, including organisation owners, never see it.
It is not a survey setting. It imports the list of available builds from Intuify's deployment platform so they can be picked from the list above, and the list it writes is shared by every organisation on the platform. Pressing it shows Syncing… until it finishes.
If the list is empty the section says "No builds registered yet. Sync from Cloudflare to import available builds." If you see that and have no sync button, it is not something you can fix from here. Ask Intuify support.
Branding & look and feel#
| Setting | What it does |
|---|---|
| Theme Color | Primary button and highlight color |
| Background Color | Full-page background |
| Logo URL | Address of the image shown at the top of the survey. A preview appears once it loads |
| Question text (px) | Size of question titles and their description text |
| Choices (px) | Size of answer, row and column labels |
| Matrix columns (px) | Size of matrix column labels only. Leave it empty and columns follow the Choices (px) size; clear it at any time to go back to following |
| Desktop +px | Added on top of whichever size applies, on wider screens only. Phones always render the base size |
| Custom CSS | Advanced styling injected into the respondent view |
Font sizes#
New surveys start at 17px for question text and for row, column and choice labels. Surveys created before this baseline keep the sizes they already had. Raising them is a deliberate change you make here, never something that happens on its own.
These are the defaults. Text you size directly in the rich text editor keeps that size and is not affected by changing the values above. To hand a piece of text back to the survey default, open the font-size dropdown in the editor toolbar and choose Default, or use Reset font sizes in a question's menu to do it for every field on that question at once.
Text you size in the editor still follows the desktop adjustment: it renders at exactly the size you typed on a phone and grows by that text's desktop adjustment on a larger screen, so it stays in proportion with the text around it. This holds on every question type, the custom interfaces included.
Matrix and Ranking questions can also override the row and column sizes for a single question, under Properties › Settings › Row & column text size, including an optional desktop adjustment that applies at 640px and above.
A single question's own Text size card#
A question can override the survey sizes from the Text size card in its properties panel. The card is grouped by the part of the question being sized, and each group offers the same two boxes:
| Box | What it sets |
|---|---|
| Size (px) | The size phones show. This is the base size for that group |
| Desktop +px | Added on top of the base on wider screens. Phones always render the base size |
There are at most four groups, one per role: the question text, the choice text, the row text and the column text. A question type only shows the groups it actually paints, so a Rating question has no row or column group.
Two behaviours worth knowing, because neither is visible on the card:
- An empty box means inherit, not zero. Clearing a box removes the override rather than storing a number, and the greyed figure that appears in the empty box is the size the question resolves to without it. Where a group reads Theme default instead of a number, that interface has no single size for the role, because its widget sizes several elements differently or sizes them relatively.
- Each group sizes only its own text. Changing the question size never moves the choices, rows or columns.
The ? button beside the card's title, labelled How text size works, shows the same summary as a tooltip.
Tip: New surveys start with a polished default theme. You can override any property or add custom CSS for full control.
Instruction bullets: list items with the
bulletclass show a small square marker in your primary color, lined up with the first line of the item's text. Change the color with--primaryColor. To reposition or resize the marker, targetli.bullet::beforein Custom CSS and mark the declarations!important.
Organization-level styling defaults may apply to new surveys in your workspace. Per-survey overrides take precedence.
Experience settings#
| Setting | Description |
|---|---|
| Show welcome screen | Show the survey title, intro text, and Start button before the first question |
| Show progress bar | Display completion percentage to respondents |
| Show question numbers | Display Q1, Q2, etc. before questions |
| Show asterisk on mandatory questions | Mark required questions with a red * in the respondent view. Turning it off only hides the marker. Required questions still have to be answered, and the builder still shows you which questions are required |
| One question per page | Show a single question at a time |
| Show back button | Turn it off to remove the Back button |
Respondent Text Customization#
Under the switches, Respondent Text Customization lets you replace any respondent-facing wording. Leave a field empty and the default translation is used. The fields are grouped, including Navigation Buttons (Start Survey, Next, Back, Submit, Continue) and Resume & Restart (Take Again, Resume, Start Fresh), alongside groups for the completion, password, email gate, status and progress screens and for validation messages. Each box shows the current default as its placeholder.
What you type here applies to the survey's base language. To word the same strings differently in another language, open the Translations tab and use System Messages there. See Multi-Language Surveys.
Response controls#
| Setting | Description |
|---|---|
| Allow partial responses | Save incomplete sessions |
| Capture screen-out responses | Keep the answer data of screened-out respondents. The screen-out itself is always counted; turn this off and only the answers are discarded. Leave it on if you may later want to mark a terminated response complete, because a promoted screen-out with no answers reaches your export as an empty row |
| Allow multiple submissions | Let the same person submit more than once on the Survey Link. Test Links can always be taken again, whatever this is set to |
| Anonymous responses | No respondent identification required |
To cap how many completes a survey accepts, use a quota rather than a setting here. See Quotas and Quota Groups.
Completion & post-survey#
| Setting | Description |
|---|---|
| Thank You Message | Text shown after submit |
| Redirect URL (optional) | Send respondents to an external URL instead |
| Email Summary | Holds one switch, Send response summary to respondent, which emails the respondent a copy of their answers after they submit |
Send response summary to respondent is greyed out and cannot be switched on while Anonymous responses is on under Responses, because an anonymous survey collects no email address to send to.
Scheduling#
The Scheduling sub-tab opens with Availability Window, which sets when your survey is available to respondents. It holds two fields, each a date picker with a time next to it:
| Setting | Description |
|---|---|
| Opens At | Leave it empty and the survey opens immediately when published |
| Closes At | Leave it empty and the survey stays open indefinitely |
Clearing the date clears the scheduled value, even though the time you typed stays in the box. Closes At cannot be set to a date in the past.
Under the window, Survey Status is a read-only line telling you the current lifecycle state of your survey: draft (being built and not yet live), published (live and accepting responses), paused (temporarily paused) or closed (no longer accepting responses).
Security#
| Setting | Description |
|---|---|
| Password protection | Require a password before the survey loads |
| CAPTCHA verification | Prevent bot submissions with CAPTCHA |
| IP address tracking | Record respondent IP addresses |
Password protection and CAPTCHA verification are marked Coming Soon and cannot be switched on yet. IP address tracking is live, and the Duplicate IPs quality filter depends on it.
Warning: Changing security or scheduling on a live survey affects new sessions immediately after you publish.
Related guides#
Was this page helpful?