> 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/releases/2025/1.172.0-22-october-2025.md). # 1.172.0 - 22 October 2025 ### Support for Multiple Custom Host Header (CHH) Aliases Per Account We’re excited to announce that accounts can now have multiple Custom Host Header (CHH) aliases, similar to the registered domains feature. The top CHH in your configuration will act as the default. This update is particularly useful if you need to update your CHH. With this enhancement, previously shared links will remain accessible as long as the CHH is still valid. *Please Note: CHH aliases are applied at the account level. This means you cannot select a specific CHH for individual forms, surveys, events, or "view online" links. The default CHH will always be used for these links, but they can still be accessed via other CHH aliases.* ### Connectors are coming soon! We’re preparing for the launch of UbiQuity Connectors, scheduled for General Availability in early 2026. As part of this work, we’ve made minor UI updates to the Database module to support upcoming connector functionality and improve overall usability. Learn more here: [**UbiQuity Connectors**](https://www.ubiquity.co.nz/connectors) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ubiquity.co.nz/releases/2025/1.172.0-22-october-2025.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.