Capabilities and requirements
Navigation destinations
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.