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

# Administration areas

> Manage users, API keys, retention, secrets, tools, workflows, and licensing.

The administrator navigation exposes configuration and monitoring screens in addition to the user-facing [Upload, Verify, and Chat](https://docs.welesai.com/guides/using-weles.md) areas. Protect administrator access and apply your organization's change-management and data-handling policies.

## Dashboard

Monitor license status, processing, operators, activity, tools, chats, and LLM usage. See [Dashboard](https://docs.welesai.com/administration/dashboard.md) for the available views and troubleshooting guidance.

## Workflows and Document Types

Use **Workflows** to create and configure ordered document-processing and agent stages. Use **Document Types** to define extraction fields, groups, prompts, and versions. Save each changed workflow stage and test with representative data before production. See [workflow stages](https://docs.welesai.com/workflows/stages.md), [document types](https://docs.welesai.com/workflows/document-types.md), and [agent workflows](https://docs.welesai.com/workflows/agent-workflow.md).

## User Config

Assign Keycloak users to the workflows they should use. Confirm each user has the appropriate identity and access, then verify the assignment with the intended user. Restrict access to workflows that process sensitive data.

## API Keys

Create a named personal API key for an integration and copy it when it is displayed. The key is shown once: store it securely and do not include it in source code or logs. Send it in the `X-API-Key` header where the API requires it. Delete the key to revoke it and update integrations when rotating credentials. See [agent workflow invocation](https://docs.welesai.com/workflows/agent-workflow.md) for an example.

## LLM Config

Configure the providers and models used for OCR and agents. Choose approved endpoints and credentials, confirm model capabilities and connectivity, and test the intended workflow. Provider API keys are stored separately from the Secrets Vault. See [AI providers](https://docs.welesai.com/administration/llm-providers.md).

## Retention

Review whether retention is enabled, the operational-data retention days, tool-details retention days, and the cleanup time in UTC. Use the calculation/preview to inspect what qualifies before running cleanup.

> [!WARNING]
>
> Manual operational cleanup deletes older data and files and can include documents stuck in processing. Tool-detail redaction removes old tool arguments and results while retaining reasoning chains. Review the preview and policy, verify backups and recovery, and ensure the action is authorized before running either operation.

## Secrets

The **Secrets Vault** stores encrypted secrets for references used by installed custom tool packages. Protect and back up the `SECRET_ENCRYPTION_KEY` according to your security and recovery procedures. Provider API keys are stored separately in the application database; do not assume that this vault key encrypts them. Avoid exposing secret values in documentation, logs, or support requests. See [configuration](https://docs.welesai.com/administration/configuration.md) and [agent tools](https://docs.welesai.com/workflows/agent-tools.md).

## Tool Manager

Install custom tool packages from trusted sources, review their requirements and permissions, and make the required secrets available. Installing a package does not automatically grant it to every agent: configure and save the tool on the appropriate agent stage. Verify external access and data handling before production. See [agent tools](https://docs.welesai.com/workflows/agent-tools.md).

## License

Inspect license status, enabled features, and expiry; activate a supplied product license as described in [licensing](https://docs.welesai.com/administration/licensing.md). Licenses do not impose a processed-data-volume quota; expiry, enabled features, and independent technical or provider limits still matter.


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