> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/changelog/2023-and-older/2023/improvements-and-fixes-december-2023.md).

# Improvements and fixes, December 2023

Improvements and bug fixes released in December 2023.

*31 December 2023*

## Improved

* **Portal:** Updated Create an Announcement page to match the Survey page. Search for Segments in Announcements now available. Editable search hint text in Customize section.
* **Editor:** Version number added to the Editor. Scrolling through full element in step visualization. Editable Guide title from Editor. Updated Guide title, Tooltip, and Tag name field designs. Updated Tooltip icons.
* **Other:** Fixed SSO initial setup for US-based customers. Updated Node.js to latest version. Added Options section to Browser Extension. Browser Extension now loads Userlane with domain and path matching.

## Fixed

* **Portal:** Fixed NPS response rate over 100%. Fixed images not showing in Announcement builder for US clients.
* **Editor:** Fixed Editor crash with appendToTarget in code selector, Userlane blocking popup actions, segmentation issues with linked Guide Tooltips, skip condition failures, empty Tags section display, and page segmentation with subdomain/path conditions.


---

# 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.userlane.com/changelog/2023-and-older/2023/improvements-and-fixes-december-2023.md?ask=<question>&goal=<user_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.