Restricted Survey Access
Restricted Survey Access lets you require an Access ID before a respondent can start your survey.
Use it when the link itself may travel widely, but you still want to decide who can begin. A client list, a conference badge list, a closed employee sample — same idea: no valid ID, no start.
You can generate short codes in Quali-Fi, or import your own IDs (and optional columns of respondent metadata) from a CSV. On restricted surveys you can also send email invitations that bind each contact to an Access ID — see Email Distribution.
Need a one-off public URL that skips the Access ID gate? Generate an Open Access Link on Distribute. The main survey URL stays restricted.
How it works
When Restricted Survey Access is enabled:
- Respondents who are not signed-in members see Enter access ID before they can begin.
- Each ID is consumed when the response starts, not when they submit. If they resume the same session, they are not asked again.
- Generated IDs are 8-character, single-use codes. Typing them is a little forgiving (letter case, and common mix-ups like O/0).
- Imported IDs are your own values: 8–64 characters, case-sensitive, and you choose how many times each one may be used.
- You can revoke an active ID so it cannot be used again. Revoking does not wipe metadata already stored on responses that started with that ID.
Note
Authenticated members going through the member portal are not prompted for access IDs.
Query values on the survey link do not override metadata that was imported with the Access ID. If you need campaign or panel tags that arrive on the URL, use Embedded Data instead — that is a different store.
Enable restricted access for a survey
Access IDs only appear on Distribute after the survey is set to restricted.
Open your survey and open Survey Settings (Tools → Survey Settings in the builder).
Under Survey Access, select Restricted (requires access ID).
Click Save Settings.
Generate and manage Access IDs
On Distribute, open Access IDs.
The dialog is split into create IDs, manage the list, and — after an import — re-download distribution links. Existing rows always show a masked code (last four characters only). Full codes appear when you first generate them, or in the distribution CSV from an import (while that file is still stored).
Generate new access IDs
Go to Distribute.
Open Access IDs.
Under Generate New Codes, enter how many you want (up to 500).
Click Generate.
Generated codes are single-use. After they appear:
- Copy Code or Link for an individual ID (the link already includes the ID so the respondent does not have to type it)
- Click Export New for a CSV of those new codes and links
Prefer sharing links. Typing an 8-character code is where most field errors happen.
Import custom Access IDs
Use Import when you already have IDs (employee numbers, sample house codes, event codes) and, optionally, extra columns you want to keep with that person.
The wizard is Import Access IDs: requirements, file, preview, field settings, confirm, then distribution CSV download.
Import upserts. New IDs are created. IDs that already exist on this survey are updated (metadata and field definitions). Uses, expiry, and revoke status are not reset. Historical responses keep the snapshot they already stored.
In Access IDs, click Import.
Optionally click Download template, then click Continue.
Click Select CSV or drag a .csv onto the dashed drop zone. Excel workbooks are not accepted. The first row must be headers, including an access_id column. Quali-Fi also accepts aid, code, id, or respondent_id.
Wait for upload and validation if the file is large. Progress shows Uploading file, then Validating rows, then Ready to configure fields. Cancel stops the job and clears the staging file.
Review the counts: Total rows, To create, To update, Invalid, File duplicates, and Data columns. Sample validation errors name the spreadsheet row and the rule (up to 25 lines). Click Configure fields.
For each extra column, set Key, Label, and Type (string, number, boolean, or date), plus PII, Exportable, and Recallable. IDs-only files are fine — you can still import with no metadata columns.
On Confirm import impact, set Max uses per ID if new IDs should work more than once (max uses applies to newly created IDs only). Treat imported IDs as sensitive is on by default (full ID masked in Raw Data unless the viewer has respondent PII permission). Click Apply import.
Download the distribution CSV (original IDs plus ready-to-send links with aid on the URL). You can download again later from Access IDs → Import distribution links until you remove the stored links file.
Imported IDs are case-sensitive. After trimming spaces on the ends, they must be 8–64 characters using only letters, numbers, and . _ ~ -. No spaces in the middle, and no other symbols.
CSV limits: 80 MB, 500,000 data rows, 50 columns, and 16 KB of extra data per row.
Invalid rows are skipped; valid rows still import. File duplicates means the same ID appears more than once in the file — the last row wins; earlier duplicates are skipped. IDs that already exist on the survey count under To update, not as errors.
Closing the dialog before Apply import finishes cancels the job. After apply, the Access IDs list still shows only masked last-four values. Full imported codes stay in the distribution CSV while that file remains stored.
Re-download distribution links
Under Access IDs → Import distribution links, Quali-Fi lists recent imports that still have a stored links file:
- Download links — download the distribution CSV again (same original IDs and survey links)
- Remove file — permanently delete the stored plaintext CSV. Imported Access IDs on the survey stay active; you cannot recover that CSV without re-importing. Use Export All for a masked last-four status list anytime.
If a row fails validation
The preview lists a sample of problems. Typical messages:
| Situation | What you’ll see |
|---|---|
| Missing ID | Access ID is missing. Each row needs an ID of 8–64 letters, numbers, or . _ ~ -. |
| Too short or too long | Access ID must be 8–64 letters, numbers, or . _ ~ - (this value has n characters). |
| Spaces or other symbols | Access ID must use only letters, numbers, or . _ ~ -. Spaces and other symbols are not allowed. |
| Same ID twice in the file | This Access ID appears more than once in the file. The last row is kept; earlier rows are skipped. |
| Already on this survey | Not an error — counted under To update. Preview notes how many existing IDs will be updated. |
| Looks like a generated code already in use | This Access ID could be confused with an existing generated Access ID. Use a different value. |
| Number / boolean / date mismatch | The column must match the type you picked (for example YYYY-MM-DD for date; true/false, 1/0, or yes/no for boolean). |
| Too much extra data on one row | This row has too much metadata. Keep each row under 16 KB. |
Missing access_id header | CSV must include an access_id column (aliases: aid, code, id, respondent_id). |
Fix those rows and upload again if you need every line. You do not have to wait for a perfect file: Apply import creates and updates only the valid IDs.
Field keys and flags
Each metadata column gets a Key (used in piping, logic, quotas, and Raw Data) and a Label (what you see in the builder). Keys must start with a letter, use only lowercase letters, numbers, or underscores, and stay at or under 63 characters. Do not start a key with sys_, q_, resp_, survey_, ed_, or aid_.
| Flag | What it does |
|---|---|
| PII | Marks the column as personal data. Recall stays off until you confirm a warning. |
| Exportable | Includes the column in CSV/SPSS when the respondent used this Access ID. |
| Recallable | Makes the value available in Insert recall / piping under Access ID data, so question text can show it to the respondent. |
PII columns default to not recallable. If you want Recallable on a PII field, tick the confirmation that you understand the value can appear in live question text.
Existing access IDs
The table lists every generated and imported ID:
| Column | Meaning |
|---|---|
| Code | Masked last four characters |
| Source | Generated or Imported |
| Fields | How many metadata columns were defined on import (0 for generated codes) |
| Status | Active, Used, Revoked, or Expired |
| Uses | How many times it has been used vs the maximum |
Revoke is available on Active IDs only. Revoking stops new starts; it does not erase metadata already stored on responses that already used that ID.
Export All downloads a status list (masked last four, source, field count, status, uses vs max). It does not include full imported IDs.
Refresh reloads the table.
Open Access Link (optional bypass)
Restricted mode stays the default. The Quick Share / custom / permanent URL still asks for an Access ID.
When you need a second URL that behaves like an open survey — a client preview, a press link, a backup for people who never received a code — generate an Open Access Link on Distribute.
Set the survey to Restricted (requires access ID) and save.
Open Distribute. The Open Access Link card appears under Quick Share.
Click Generate open access link.
Copy the URL, or click Open Survey to test it.
The open-access URL uses a distinct code (/s/oa-…). It is not the custom vanity slug and not the permanent short code.
Once a link is active:
- Copy Link / Open Survey — share or preview the bypass URL
- Regenerate — the current open-access URL dies immediately; anyone still holding the old one needs an Access ID again
- Revoke — same cutoff, without creating a replacement
Rules that matter in the field:
- The primary restricted URL still requires an Access ID. Do not assume “restricted” is off because the open-access URL works.
- People who enter through the open-access URL have no Access ID metadata. Piping, logic, and quotas that depend on
aid.fields will not have values for those responses. - Switching the survey back to Open link (no access ID) clears the open-access code.
- Ordinary
?id=fallback never inherits open-access privileges. A stale vanity URL does not become a bypass.
Treat this like a spare key. Generate it when you need it, revoke it when you do not.
Email invitations on restricted surveys
Distribute → Send to Email List can bind each contact to a matched or generated Access ID. Pick Contact field with Access ID (External ID or a custom field), review match / generate / issue counts, then confirm before send. Invitation URLs stay signed — they do not put a plaintext Access ID in the link.
The same Access ID panel appears on Email → Campaigns when you attach a restricted survey in Settings. Confirm bindings on Review before Send, Schedule, or test send.
Full steps: Email Distribution.
Respondent experience
If someone opens a restricted survey without a valid ID in the link, they see Enter access ID.
They can:
- Type or paste the ID and click Continue
- Use a link you copied or exported from Access IDs, which already includes the ID as
aid(the link may also useaccess_id) - Open a personalized email invitation link (signed; no plaintext
aidin the URL) when you sent from Send to Email List
Invalid, revoked, already-used (when the use limit is reached), or expired IDs show an error and the survey does not start. Imported IDs must match exactly, including letter case.
Use Access ID data in the survey
Imported columns appear in the Survey Builder as Access ID data — for piping, and as a condition source in logic, quotas, filters, and related rules.
Piping / recall
Columns marked Recallable appear under Insert recall / piping → Access ID data. Pick a field the same way you pick an embedded-data field.
Typical uses:
- Greet someone with a segment or site name you already know
- Confirm which wave or list they were invited on, without asking again
Only recallable fields resolve for respondents. This is separate from embedded data (ed. fields) and from question recall.
See Piping and Recall for the insert menu.
Logic, quotas, and filters
Choose Access ID data as the condition source, then pick the field key. Operators follow the field type (same idea as embedded data). Values come from the respondent’s Access ID snapshot at start — not from live edits to the Access ID list, and not from URL query parameters.
In Quota Management bulk import, write conditions like aid.city="brampton". See also Survey Logic & Branching.
Generated IDs with no metadata fields do not expose this source.
Raw Data and exports
Raw Data still has an AID column for the access ID used on that response.
Imported metadata appears in additional columns immediately after AID, named aid_ plus the field key (for example aid_segment). Responses that started before you imported fields, or that used a generated ID with no metadata, show those cells empty.
CSV and SPSS include Exportable Access ID fields when you have permission to export that data. PII-classified columns follow respondent PII rules. If Treat imported IDs as sensitive was on, the Access ID itself is masked in Raw Data for people without respondent PII permission. Generated codes are not treated that way.
Revoking an ID does not erase snapshots already stored on responses.
Tips
- Generate or import a few extras so a mistyped send does not stall fieldwork.
- Keep the distribution CSV (or re-download from Import distribution links) with your other sample files — not in a ticket screenshot.
- To halt new completes quickly, revoke remaining Active IDs rather than taking the survey offline if you still need in-progress sessions to finish.
- Do not turn on Restricted (requires access ID) for standard panel audience entry links. Panels use
rid(panelist ID), not survey Access IDs. Raw Data AID is the survey Access ID; panelist identifiers appear separately (often as RID or embedded data).