> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cortex-labs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# What Kato can do

> Look up Kato's capabilities, required scope, approval boundaries and task guides.

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

| Capability | Supply or check | Guide |
| - | - | - |
| Product help | Your goal and the part of the platform you need to understand. Help results use the sections you are entitled to read. | [Your first task](/kato/first-task) |
| Find resources | Resource kind, name, relevant workspace and identifier where available; current read access. | [Find and track work](/kato/find-and-track-work) |
| Open a page | The identified target and its required IDs; the destination still checks access. | [Getting around Cortex](/getting-started/navigate-the-app) |
| Prepare resources | Explicit target, creation/update authority, security level, audience and valid dataset attachments. | [Prepare a workspace](/kato/prepare-workspace) |
| Configure ingestion | Supported source, target dataset, collection scope, authorised secret reference, parameters and limits. | [Set up ingestion](/kato/set-up-ingestion) |
| Author definitions | Draft ownership, supported definition/block kinds, compatible dependencies and selected versions. Kato can help with prompts, enrichments, workflows and app configuration. | [Build a workflow](/kato/build-workflow) |
| Evaluate an enrichment | Permitted sample scope, provider limits, assessment criteria, test isolation and usage limits. | [Develop an enrichment](/kato/develop-enrichment) |
| Apply an enrichment | Selected published version, dataset scope, authorised principal and separate binding/processing choices. | [Develop an enrichment](/kato/develop-enrichment#apply-it-deliberately) |
| Start a workflow | Definition/version, target workspace, permitted inputs, execution authority and current limits. | [Build and test a workflow](/kato/build-workflow) |
| Track work | Read access to the resource, evaluation or submitted run; inspect outputs and decisions separately. | [Find and track work](/kato/find-and-track-work) |

## 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

| Operation | Boundary |
| - | - |
| Read permitted resources | Uses your current authority. |
| Ordinary content creation or updates | Can proceed when you request them and have permission; a separate approval card is not required for every write. |
| Delete, archive, hide, cancel or revoke | Requires a gated approval for the specific request. |
| Access, membership, role, sharing or security-level change | Requires a gated approval and the normal permission/clearance checks. |
| Publish, send externally, decide a review or merge identities | Requires current authority and Kato's approval card. The relevant operation also records its own version-specific outcome. |
| Change standing agent instructions, shared agent settings or other people's reading/spending context | Requires the applicable authority and gated approval. |
| Password, session, MFA or API-key management | Unavailable to Kato. Use the appropriate secure account or administration interface. |

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](/kato/recover-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](/kato/context-and-permissions).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.