> For the complete documentation index, see [llms.txt](https://docs.talentmap.com/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talentmap.com/knowledge-base/general/product-updates/september-15th-2026.md). # September 15th, 2026 ### Set Your Logo Once and Use It on Every Survey Your organization's logo is now held at the organization level, so every survey created under it picks the logo up automatically. You can still use a different logo on an individual survey when you need to. **What's new:** Upload your logo once in your organization settings and it applies to every survey created under that organization, with no upload step when a survey is created. To use a different logo on one survey, set a logo on that survey and it takes precedence over the organization logo for that survey only. Logo files are now capped at 1 MB. **Why it matters:** Two problems, one change. Uploading the same logo on every new survey was repeat work that got skipped, which is how surveys went out unbranded. Separately, a very large logo file used to slow the designer to a crawl, because the image reloaded every time a survey was opened or edited. The 1 MB cap prevents that, and it is a generous ceiling: a logo sized for a survey page is normally well under it. **How to use it:** Upload your logo in your organization settings. New surveys pick it up with no further action. To override it on a single survey, open that survey, click **Design Survey**, and add a logo there. If your file is over 1 MB, export it again at a smaller size, or save it as a JPEG instead of a PNG. ### Add a Question Anywhere on a Page You can now insert a question between any two questions already on a page, instead of adding it at the end and moving it into position. **What's new:** The **Add Question** control works at any position on a page, not just the bottom. Pick the spot you want, choose your question type, and the new question lands there. The questions around it keep their order and their content. **Why it matters:** Adding one question in the middle of a finished page used to mean adding it at the end, collapsing the page, and dragging it up past everything else. On a 20 question page that is a slow and error-prone piece of housekeeping for a one question change. Stakeholder review almost always produces exactly that kind of change, late. **How to use it:** Open your survey and click **Design Survey**. Click **Add Question** where it appears between two existing questions, then select the question type you want. ### See Page and Question Names Instead of System IDs The questionnaire design page now refers to your pages and questions by their titles, so you no longer have to decode a long string of characters to work out what you are looking at. **What's new:** Page references show the page title or page number, and question references show the question title. The internal system IDs are gone from the design page. **Why it matters:** Those IDs meant that anyone building a questionnaire had to keep a mental map between a string and "Engagement". It slowed down editing and it made mistakes easy, particularly on long surveys with similar page names. **How to use it:** Nothing to turn on. Open **Design Survey** and the titles are there. --- # 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.talentmap.com/knowledge-base/general/product-updates/september-15th-2026.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.