> For the complete documentation index, see [llms.txt](https://docs.probe.splx.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.probe.splx.ai/updates/product-updates/february-2025.md). # February 2025 ## Workspaces Organization admins and owners can now create Workspaces to group AI targets under a shared context. Users can be assigned to specific workspaces, making it easier to manage access, isolate environments, and organize targets by team, project, or function. ## Improvements & Tweaks * When configuring prompt hardening, users can now open the latest probe results directly from the probe selection table. * Option to delete files uploaded in probe configurations. * Option to delete uploaded Log Analysis batches. * Target integrations, which connect the platform to the testing target, have been renamed Target Connections to avoid confusion with platform integrations (e.g., JIRA). * Direct links to relevant documentation pages have been added to each target connection in Target Settings. --- # 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.probe.splx.ai/updates/product-updates/february-2025.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.