Skip to main content
Kato is the platform assistant available to every signed-in user. It answers product questions and operates permitted resources with your authority. The normal usage quota applies. Kato’s availability does not itself grant Vantage access or permission for an operation.

Capabilities and requirements

Kato can request navigation to a workspace, dataset, workflow, workflow run, review queue, app instance, app template, enrichment, chat, chat project or billing page. It needs the identifiers for that destination. Related records without a direct navigation destination are inspected through their owning resource. Opening a page does not grant access or wait for all background work to finish. Returning to an old Kato reply does not automatically repeat its navigation request.

Changes and approval

The approval card offers Approve and Deny. Check the operation and server-provided request details, including the target. Truncated or unavailable details need clarification before approval. Approval applies to that request in that Kato conversation. A different target requires another approval. A used or expired request cannot be approved again. Agreement to a proposed setup defines the changes you want. It is separate from an access-change approval, a review decision and publication. Collection, automatic processing, run starts and publication remain explicit choices in the task you give Kato.

Usage and results

Kato conversation usage is attributed to you under Arc. Submitted collection, evaluation, enrichment and workflow work follows its own resource and usage rules. Check the relevant work record for actual results and usage. Kato’s reply is not proof of complete setup, successful processing or supported evidence. Open the resource and inspect the result. See Recover an incomplete task when a dependency, limit or failure stops the work. For the relationship between your request, the open page and the target resource, read How Kato uses context and permissions.