The Admin Panel is where administrators control what IntraLLM can do, who can do it, and how it behaves. Open it from Admin Settings in the account menu — it appears only for accounts with administrator permission.
What the Admin Panel covers
The panel is organised into sections, each controlling one area of the platform:
| Section | What you control | Guide |
|---|---|---|
| General | Platform defaults: instance name, language, registration, sharing, banners | General |
| Interface | Workspace-wide interface defaults for every user | Interface |
| Connections | Model endpoints (local services, OpenAI-compatible APIs) | Connections |
| Models | Which models exist and who may use them | Models |
| Training | Fine-tuning capability and its limits | Training |
| Tools | Tool servers the assistant can call | Tools |
| Audio | Voice and transcription services | Audio |
| Images | Image generation availability and settings | Images |
| Videos | Video generation availability and settings | Videos |
| Documents | Document processing features and engines | Documents |
| Search | Web search providers and policy | Search |
| Code | Code execution (interpreter) policy | Code |
| Evaluations | Model quality feedback and the leaderboard | Evaluations |
| Agentic | Agentic workflows and deep-agent capability | Agentic |
| Users & Groups | Accounts, groups, and what groups can see | Users & Groups |
| Permissions | Fine-grained feature access per group | Permissions |
| Model Pricing | Cost rates that drive usage reporting | Model Pricing |
| Licensing | Your licence, its status and features | Licensing |
| Guardrails | Policy checks on inputs and outputs | Guardrails |
| Reset Admin Password | Recovery when administrators are locked out | Reset Admin Password |
How the sections interact
A capability reaching a user's screen passes three gates:
- The feature is enabled in its capability section (for example Videos is on).
- A resource is connected — an endpoint, provider, or engine configured (a video model exists).
- The user's group has permission to use it (Permissions).
When users report "I can't see X", check those three gates in order.
First-week checklist for new administrators
- Confirm licence and features — Licensing.
- Connect and test model endpoints — Connections.
- Create groups that mirror your org and set permissions — Users & Groups, Permissions.
- Decide capability defaults conservatively — enable what the pilot needs; widen later.
- Set the workspace defaults in General and Interface (registration policy, themes, history).
- Review Guardrails against your policies.
- Set Model Pricing rates so usage reporting is meaningful.
- Run the Initial Setup checklist end-to-end with a pilot user.
Change discipline
- Capability changes apply workspace-wide — make them deliberately, and tell user groups when behaviour changes.
- Where a section supports per-group settings, prefer restricting by group over disabling globally.
- Pair every powerful capability (tools, code execution, agentic) with the governance pages before rollout.