> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/documentation/data-capture/surveys/details-and-settings.md). # Details and Settings Survey details and settings control how your survey behaves, including when it closes, how many times someone can respond, and how it looks to respondents. You can update the name, description, and tags for your survey at any time by going to **Edit Survey Details and Settings**. The survey URL is also visible here and on the Survey Dashboard. ### Close Settings **Date** sets a date after which the survey will automatically close. Anyone trying to access it after this date will see the Inactive page. **Responses** closes the survey once a set number of responses has been reached. Anyone currently completing the survey when the limit is reached will still be able to finish. *** ### Response Limits **Allow multiple responses** is the default. Respondents can complete the survey as many times as they like. **Only allow one response** uses cookies for anonymous respondents and personalised links for contacts arriving via UbiQuity Mail to prevent duplicate responses. Note that on a shared computer, this setting may prevent new respondents from completing the survey. **Allow further responses after a period of time** works like the one response limit but reopens the survey to the same respondent after a set period. This is useful for pulse surveys or recurring NPS programmes. *** ### Save and Resume Allows respondents to leave the survey and come back to it later without losing their progress. For anonymous respondents this uses a cookie. For contacts arriving via a UbiQuity email it uses their personalised link. If you expect respondents to be on public computers and entering sensitive information, save and resume is not recommended. *** ### Survey Access **Accessible to anyone with the link** is the default open access setting. **Restrict access to allowed IP addresses** limits access to the IP addresses configured for your UbiQuity account. Contact UbiQuity to manage this list. **Restrict access to a custom IP address whitelist** lets you specify your own list of permitted IP addresses. **Restrict to database contacts only** means anonymous links will show the Inactive page. Only personalised links from UbiQuity mailouts will work. *** ### Numbering and Layout Options You can configure how questions and pages are numbered, including dynamic numbering that keeps numbers sequential even when logic skips pages, and consecutive numbering across pages. Layout options include showing or hiding a progress bar, enabling or disabling the back button, and showing or hiding asterisks on mandatory questions. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ubiquity.co.nz/documentation/data-capture/surveys/details-and-settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.