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

# Roles and Daily Use

> Roles and Daily Use for EXT:ns_t3af (T3AF).

Practical guidance for editors, administrators, and stakeholders using **T3AF** (`EXT:ns_t3af`) in daily workflows.

## For administrators

Daily responsibilities:

* Keep provider API keys valid in T3AF > AI Providers.
* Maintain the default provider and model selections.
* Monitor usage statistics across all configured AI providers in T3AF > AI Usage and the Dashboard.
* Keep credentials and access permissions under control.

### Admin checklist

1. Confirm a default provider is enabled in **AI Providers**.
2. Run **Test connection** on critical provider rows.
3. Test extension-dependent AI features in your connected modules.
4. Review provider usage statistics regularly (requests, tokens, and consumption) for cost and rate control.

## For editors

Editors usually do not configure providers directly. They interact with features built by other extensions that depend on T3AF.

When AI features fail in a backend module:

* Retry once.
* Capture exact error text.
* Inform the administrator with module and page context.

## For non-technical stakeholders

T3AF helps organizations by:

* Reducing duplicated AI integration work across extensions.
* Centralizing provider and model governance.
* Improving consistency of AI capabilities across teams.

## What to expect operationally

* Some providers have rate limits and temporary outages.
* Model behavior can differ between providers and versions.
* Usage statistics cover configured AI providers from a centralized view and may be cached (not always real-time).

## Known boundaries

* No standalone frontend plugin is provided by this extension.
* This package is a service layer; UI features come from dependent extensions.