The August 2026 release adds the Tricentis Product Expert to Tosca Cloud documentation, giving release owners faster access to product guidance without moving between documentation sites.
The release also extends the contributor role: contributors can now delete assets and folders in Organize your inventory. That is a useful operational change, but it needs deliberate permission governance where automation assets are shared across teams.
Rollout timing may vary by a few days between environments.
Documentation answers in the delivery workflow
The Tricentis Product Expert is available in the Tosca Cloud documentation experience. Teams can ask broad questions, such as recommended test data management practices, or request specific procedural guidance, such as steps for comparing PDF files.
The assistant is grounded across Tricentis manuals and can answer cross-product questions, including how Tosca Cloud works with qTest. Documentation search now also begins with an AI-generated summary, reducing the need to open multiple search results before finding an initial answer.
For enterprise delivery organizations, the operational value is reduced research overhead during test design, failure analysis, onboarding, and integration planning. Senior practitioners should treat the output as guided product research, not as an automatic change approval.
Recommended controls include:
- Validate guidance against the tenant’s configuration and product versions.
- Keep architecture, security, and test-data decisions subject to existing review gates.
- Define when teams must retain links or evidence for implementation decisions.
- Update internal runbooks when recurring documentation questions reveal process gaps.
Contributor deletion rights require ownership discipline
Contributors can now delete assets and folders from Organize your inventory. This can reduce clutter and help teams retire obsolete test artifacts more quickly.
However, deletion access changes the risk profile of the contributor role. In a shared inventory, an apparently unused module, reusable test step, or folder may still support active test cases, scheduled playlists, or another team’s maintenance process.
Before enabling or broadening contributor access, QA platform owners should review:
- Which workspaces contain shared or business-critical assets.
- Who owns modules, test cases, reusable test steps, and folder structures.
- Whether teams have a defined review path before deleting shared content.
- How role assignments align with separation-of-duties and audit requirements.
- Whether deletion procedures distinguish obsolete assets from assets needing remediation.
The release does not replace asset lifecycle governance. It makes clear ownership and role design more important.
What release owners should do now
Start with a focused validation rather than a tenant-wide process change. Confirm that the documentation assistant and contributor deletion capability are available in each relevant environment, then test the expected workflow with representative users.
A practical adoption sequence is:
- Identify contributor groups and the inventories they can access.
- Classify shared libraries and critical automation assets.
- Define deletion approval expectations for each workspace type.
- Pilot the documentation assistant with common support and test-design questions.
- Update onboarding material, role matrices, and operating procedures.
This approach keeps productivity gains from becoming an avoidable governance issue.
Governance and audit considerations
The documentation enhancement can help teams reach answers faster, but it does not create authoritative approval for production changes. Decisions affecting security, test data, integrations, or regulated workflows should still follow documented engineering and change-management controls.
For contributor deletion permissions, governance should answer three direct questions: who can delete, what may be deleted, and how teams detect or address an incorrect removal. Those answers need to be consistent across QA, DevOps, DevSecOps, and application ownership groups.
How Merito helps
Merito helps enterprises assess Tosca Cloud role models, inventory ownership, and release-adoption controls. We can run a permission review, define practical asset lifecycle standards, and integrate AI-assisted documentation use into existing QA and DevSecOps governance without slowing delivery.
Merito is an authorized Tricentis reseller and services partner, listed as a Certified Solution Partner in the Tricentis partner directory. Our Tricentis Tosca Cloud team can scope licensing, sizing, and rollout for August 2026, and our enterprise upgrade services help you plan and validate the upgrade with minimal disruption to release schedules.