> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/changelog/readme/2025-10.md). # October 2025 5 product updates shipped in October 2025. See [Product Updates](/changelog/readme.md) for the latest. {% updates format="full" %} {% update date="2025-10-26" %} ## New Predefined Roles and Seat Management #### What's new? * Two new predefined roles are now available: Associate and Observer, giving you more granular control over team member permissions. * A redesigned seat management experience makes it easier to manage who has access and at what level. #### Why this matters? * With more role options, you can tailor access levels to match how different team members actually use the platform, improving security and reducing noise for those who only need limited visibility. #### Availability * Available for accounts on the enterprise (DAU-based) pricing plan. {% endupdate %} {% update date="2025-10-22" %} ## APM Flows: Android Occurrences Connected to Session Replay #### What's new? * Android APM Flow occurrences are now linked to Session Replay. You can click "View Session" on any occurrence to watch the full session that led to the issue. * This was already available for iOS and is now extended to Android. The connection works retroactively on older occurrences as well. #### Why this matters? * You no longer need to guess what happened before a performance issue on Android. Session Replay gives you the full visual context alongside your APM data. {% endupdate %} {% update date="2025-10-13" %} ## New Logs Experience in Session Replay #### What's new? * Session Replay now features a redesigned logs experience with improved readability, navigation, and overall usability. * Logs within session recordings are easier to scan and follow, helping you trace user actions and events more efficiently. #### Why this matters? * Debugging sessions becomes faster when you can clearly read and navigate through logs alongside the visual replay, reducing the time it takes to identify root causes. {% endupdate %} {% update date="2025-10-13" %} ## Copy Alerts Between Apps #### What's new? * You can now copy alerts from one app or environment to another, removing the need to manually recreate alert configurations. * Import your existing alert setups across apps and environments in just a few clicks. #### Why this matters? * Managing alerts across multiple apps and environments is significantly faster, especially for teams with shared alert configurations across staging and production. {% endupdate %} {% update date="2025-10-05" %} ## Hourly Timestamp Filtering & Flow Filter in Session Replay #### What's new? * You can now filter sessions by a specific hour on a specific day using the enhanced date filter. * A new Flow filter lets you find all sessions where end users passed through a specific flow. #### Why this matters? * Narrowing down sessions to a precise timestamp helps you quickly find the exact session you are looking for without scrolling through irrelevant data. {% endupdate %} {% endupdates %} --- # 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.luciq.ai/changelog/readme/2025-10.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.