# Teams, smarter chat runs, and visual element matching

> 12 updates: Access control and session security hardened, API-created conversations attributed to API key owner, Change review shows an error when the…

Source: https://qa.tech/changelog/2026-05-27

---
12 updates shipped on May 27, 2026.

In this release

1.  01[Access control and session security hardened](#2026-05-27-access-control-session-hardening)
2.  02[API-created conversations attributed to API key owner](#2026-05-27-api-conversations-attributed-to-key-owner)
3.  03[Change review shows an error when the page can't be fetched](#2026-05-27-change-review-fetch-error)
4.  04[Chat now runs suggested tests in a single run](#2026-05-27-chat-suggested-tests-single-run)
5.  05[Test sessions no longer missing from chat](#2026-05-27-chat-test-sessions-missing-fixed)
6.  06[Issues weren't being created on test runs – fixed](#2026-05-27-issues-creation-fixed)
7.  07[Onboarding error fixed](#2026-05-27-onboarding-error-fixed)
8.  08[Organization domains with DNS verification and auto-join](#2026-05-27-organization-domain-verification-auto-join)
9.  09[Outbound IP list updated](#2026-05-27-outbound-ip-list-updated)
10.  10[Auth-gated preview deployment URLs now work correctly](#2026-05-27-preview-deployment-auth-gate)
11.  11[Teams management in organization settings](#2026-05-27-teams-management)
12.  12[Agent finds UI elements using visual descriptions](#2026-05-27-visual-element-descriptions)

1.  Update 01 of 12
    
    ## Access control and session security hardened
    
    Routes and cookies were tightened as part of a broader security review.
    
    OAuth integration endpoints now enforce stricter access controls, closing a path where one account could interfere with another's active connection. Session cookie protections were also improved.
    
    [\# Direct link](#2026-05-27-access-control-session-hardening)
    
2.  Update 02 of 12
    
    ## API-created conversations attributed to API key owner
    
    Conversations started through the public API now show the correct owner instead of a generic system account.
    
    Conversations started through the public API now show the correct owner instead of a generic system account. When a conversation is created via the API using an API key, it is now attributed to the user who owns that key. This is reflected in the `created_by` field on conversations and is visible in audit history.
    
    [\# Direct link](#2026-05-27-api-conversations-attributed-to-key-owner)
    
3.  Update 03 of 12
    
    ## Change review shows an error when the page can't be fetched
    
    Instead of stalling silently, change review now surfaces a clear message when a fetch fails.
    
    If a change review is triggered on a page behind authentication or an otherwise unreachable URL, it now shows an explicit error rather than leaving the UI in an unclear state.
    
    [\# Direct link](#2026-05-27-change-review-fetch-error)
    
4.  Update 04 of 12
    
    ## Chat now runs suggested tests in a single run
    
    Test cases suggested by the chat agent now execute together instead of as separate test runs.
    
    When you asked the chat agent to run a set of suggested test cases, they previously spawned as multiple independent runs – one per group. They now run as a single coordinated test run, making results easier to review in one place.
    
    [\# Direct link](#2026-05-27-chat-suggested-tests-single-run)
    
5.  Update 05 of 12
    
    ## Test sessions no longer missing from chat
    
    The chat view now loads test run sessions correctly when browsing a test suite.
    
    In some cases, opening a test suite from chat would show no sessions even when runs existed. The underlying fetch is now accurate and sessions appear as expected.
    
    [\# Direct link](#2026-05-27-chat-test-sessions-missing-fixed)
    
6.  Update 06 of 12
    
    ## Issues weren't being created on test runs – fixed
    
    Test failures now correctly generate issues again.
    
    A regression caused issues to stop being created when test runs completed. The trigger that creates issues from failed tests has been restored.
    
    [\# Direct link](#2026-05-27-issues-creation-fixed)
    
7.  Update 07 of 12
    
    ## Onboarding error fixed
    
    Some new sign-ups hit an error during onboarding. Fixed.
    
    A query error introduced with recent changes caused the onboarding flow to fail for some users. The underlying issue has been corrected.
    
    [\# Direct link](#2026-05-27-onboarding-error-fixed)
    
8.  Update 08 of 12
    
    ## Organization domains with DNS verification and auto-join
    
    Verify your domain and let new teammates auto-join your organization on sign-in – no invitation required.
    
    Teams can now verify their domain and have new teammates auto-join on sign-in – no invitation required. Under Settings → Authentication, you can add your organization's domain (e.g. `company.com`) and prove ownership with a DNS TXT record at `_qatech-verification.<yourdomain>`. Once the record resolves, anyone who signs in with a matching email address is automatically added to your organization. Public email providers (Gmail, Outlook, and similar) are blocked from this flow. The domain management screen shows verification status and the exact DNS record to add.
    
    [\# Direct link](#2026-05-27-organization-domain-verification-auto-join)
    
9.  Update 09 of 12
    
    ## Outbound IP list updated
    
    A new outbound IP has been added to QA.tech's published IP list. Refresh your allowlist.
    
    A new outbound IP has been added to QA.tech's published IP list. If your app restricts inbound traffic by IP, refresh your allowlist from the canonical source: `/.well-known/qatech-ips.json`. The up-to-date list is always available there.
    
    [\# Direct link](#2026-05-27-outbound-ip-list-updated)
    
10.  Update 10 of 12
     
     ## Auth-gated preview deployment URLs now work correctly
     
     Test runs against preview platforms with an auth gate no longer stall at the gate.
     
     Testing apps on preview platforms that gate URLs behind an authentication screen no longer stalls at that gate. QA.tech now automatically handles the bypass for known preview-deployment patterns, so test runs proceed past the preview screen without manual workarounds.
     
     [\# Direct link](#2026-05-27-preview-deployment-auth-gate)
     
11.  Update 11 of 12
     
     ## Teams management in organization settings
     
     Organizations can now create teams and assign members to them from Settings.
     
     A new Teams section in organization settings lets you group members into named teams. From the "Edit member" flow you can assign or remove team memberships directly. Teams are also available as context in the chat agent, so you can scope conversations and test runs to a specific team.
     
     [\# Direct link](#2026-05-27-teams-management)
     
12.  Update 12 of 12
     
     ## Agent finds UI elements using visual descriptions
     
     The agent can now match descriptions of how something looks to actual screenshots of your site.
     
     When generating or running tests, the agent can now locate elements using visual descriptions – "the eye icon", "the blue submit button" – by matching them against screenshots captured during site crawls. This improves test accuracy on elements that lack clear accessible labels.
     
     [\# Direct link](#2026-05-27-visual-element-descriptions)
     

## Your team moves fast. Can your testing keep up?

QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo.

[Get a demo](https://qa.tech/demo)

[QA.tech](https://qa.tech/)

SOC 2 Type 2 compliant

![Sensiba SOC 2 Type 2 compliant](https://qa.tech/assets/soc2-type2-badge-DPb1j9VX.png)

### Product

-   [Platform overview](https://qa.tech/product)
-   [AI QA Testing](https://qa.tech/ai-qa-testing)
-   [Web Testing](https://qa.tech/product/web-testing)
-   [Mobile Testing](https://qa.tech/product/mobile-testing)
-   [PR Testing](https://qa.tech/product/pr-testing)
-   [MCP](https://qa.tech/product/mcp)
-   [Use cases](https://qa.tech/use-cases)
-   [Changelog](https://qa.tech/changelog)

### Compare

-   [QA.tech vs Cypress](https://qa.tech/compare/qa-tech-vs-cypress)
-   [QA.tech vs Playwright](https://qa.tech/compare/qa-tech-vs-playwright)
-   [QA.tech vs Mabl](https://qa.tech/compare/qa-tech-vs-mabl)
-   [QA.tech vs QA Wolf](https://qa.tech/compare/qa-tech-vs-qa-wolf)
-   [AI vs Human QA](https://qa.tech/saas)

### Resources

-   [Docs](https://docs.qa.tech/)
-   [Blog](https://qa.tech/blog)
-   [Events](https://qa.tech/events)
-   [Pricing](https://qa.tech/pricing)
-   [Case Studies](https://qa.tech/case-studies)

### Company

-   [About](https://qa.tech/about-us)
-   [Partnerships](https://qa.tech/partnerships)
-   [Press](https://qa.tech/press)
-   [Contact Us](https://qa.tech/contact)
-   [Privacy Policy](https://qa.tech/privacy-policy)
-   [Terms of Service](https://trust.qa.tech/resources?s=mb9w4yjb03i3t8bjsq4jx3&name=main-agreement.pdf)
-   [Security & Compliance](https://trust.qa.tech/)

### Social

-   [](https://www.linkedin.com/company/qa-tech-ai/)
-   [](https://x.com/getqatech)
-   [](https://www.instagram.com/getqatech/)

© 2025 QA.tech. All rights reserved