> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/clarity-lims/clarity-lims-v6.3-and-lablink-v2.5/readme/release-notes-clarity-lims-v6.3.2.md). # Release Notes Clarity LIMS v6.3.2 Published: July 2025 Last Update: September 2025 Latest Release: v6.3.2 This Release Notes describe the key changes made to software components for Clarity LIMS v6.3.2. The Clarity LIMS v6.3.2 patch release supersedes v6.3.1. It is intended for customers on or migrating to Clarity LIMS v6.3.2. {% hint style="info" %} Note: All customers on Clarity LIMS v6.2.1, v6.3.0 and v6.3.1 are strongly recommended to upgrade their instance(s) to Clarity LIMS v6.3.2. {% endhint %} This release resolves customer-reported issues related to the following functions: * Well plates on Placement screen rendering too big in Clarity v6.3.0 and v6.3.1. * Valid SSH usernames are rejected when trying to create SSH access. ### New Features There are no new features added with this release. ### Updates * The Placement UI has been improved to proportionally display both container and Sample list table on screen. Wells for container with 384-well format are now displayed in full. * PostgreSQL has been updated from v15.7 to v15.13. ### Bug and Security Vulnerability Fixes * Fix a bug where SSH request made through System Settings, do not allow capital letter case and number as starting character of the provided username. * Fix a bug where localhost\_access\_logs files are not being deleted, causing access logs to be preserved indefinitely on Clarity v6.3.1. * Fix a bug where the position of tooltips for esignature on Record Details screen has shifted away from the green quill icon following real estate expansion in Clarity v6.3.0. * Fix a bug where deleted label group still appear on ice-bucket label group dropdown option on Queue screen. * Fixed security vulnerabilities. ### Known Issues Refer to [Known Issues for Clarity LIMS v6.3](/clarity-lims/clarity-lims-v6.3-and-lablink-v2.5/readme/known-issues-v6.3.x.md) for list of known issues for Clarity LIMS v6.3. ### Additional Notes Refer to [Additional Notes for Clarity LIMS v6.3](/clarity-lims/clarity-lims-v6.3-and-lablink-v2.5/readme/additional-notes-v6.3.x.md) for list of additional notes for Clarity LIMS v6.3. The following are additional notes applicable to Clarity LIMS v6.3.2: * PostgreSQL 15.13 is now qualified to run in Clarity LIMS v6.3.2. * PostgreSQL 15.14 has been assessed to be at low risk of security vulnerabilities and has been shown to have no functional impact on Clarity LIMS v6.3.2. --- # 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://help.bioinsight.illumina.com/clarity-lims/clarity-lims-v6.3-and-lablink-v2.5/readme/release-notes-clarity-lims-v6.3.2.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.