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

# AI Studio Administrator

> Overview of the AI Studio Administrator persona in Tyk AI Studio

The **AI Studio Administrator** is the primary manager of the Tyk AI Studio installation. This persona is responsible for the operational integrity, security, and financial governance of the AI platform. They ensure that AI resources are available, secure, and used within budget.

## Lifecycle

The typical lifecycle of an AI Studio Administrator involves four key stages:

1. **Configure**: Setting up the fundamental infrastructure, including connecting to [LLM Providers](/5.12/ai-management/ai-studio/llm-management) (e.g., OpenAI, Anthropic) and configuring [Vector Databases](/5.12/ai-management/ai-studio/datasources-rag) for RAG.
2. **Govern**: Establishing global guardrails, such as [Policies](/5.12/ai-management/ai-studio/filters) for PII masking, rate limiting, and role-based access control (RBAC).
3. **Onboard**: Creating [Teams](/5.12/ai-management/ai-studio/teams) and [Users](/5.12/ai-management/ai-studio/user-management), assigning roles, and allocating resource quotas.
4. **Monitor**: Continuously tracking organization-wide token usage, enforcing [Budgets](/5.12/ai-management/ai-studio/budgeting), and auditing security alerts via the [Dashboard](/5.12/ai-management/ai-studio/analytics).

## Core Features

### Provider Management

Centralized management of LLM credentials and configurations. Admins can add, update, or deprecate models from providers like OpenAI, Anthropic, or Mistral without requiring changes to consumer applications.

* **Key Capability**: Unified API key management (stored as [Secrets](/5.12/ai-management/ai-studio/secrets)) to prevent credential sprawl.

### Policy & Security

Enforcement of global security and compliance rules.

* **PII Detection**: Automatically redact sensitive information (credit cards, emails) from prompts before they reach the LLM.
* **RBAC**: Granular control over which teams can access specific models or tools.
* **Rate Limiting**: Protect upstream provider quotas by limiting requests per user or app.

### Cost Management

Comprehensive financial controls to prevent "bill shock."

* **Budgets**: Set monthly spending limits at the Organization, Team, or App level.
* **Alerts**: Receive notifications when spending approaches defined thresholds (e.g., 80% of budget).
* **Chargeback Reporting**: Detailed analytics to attribute costs to specific teams or projects.

### Audit Logs

Full traceability of system access and configuration changes.

* **Access Logs**: Track who accessed which model and when.
* **Configuration History**: Audit trail of changes to policies, budgets, and provider settings.