> For the complete documentation index, see [llms.txt](https://docs.blockbrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockbrain.ai/for-builders/manage-bot-access/ai-model-and-agents-availability-control.md).
# AI Model and Agents Availability Control
Control which LLMs and Agents are available to your bot users. Set a permitted list of models and agents, or restrict users to the bot's default selection.
#### Overview
The **AI Models** section in Bot Settings lets **bot owners** and **bot editors** control which LLMs and Agents are available to bot users. The redesigned interface provides two dedicated sections:
* **Manage LLM Availability**: control which Large Language Models users can select
* **Manage Agent Availability**: control which Agents users can select
Both sections offer a toggle to allow all available options, or a customizable permitted list that restricts access to only the models and agents you choose.
***
#### Prerequisites
* You must have the **Bot Owner** or **Bot Editor** role for the bot you want to configure
* The LLMs and Agents you want to make available must already be enabled for your platform by your admin
***
#### How It Works
Each availability section has two modes:
| Mode | Behavior |
| --------------------------------- | --------------------------------------------------------------------------------- |
| **Allow all available** (default) | All platform-enabled LLMs or Agents are accessible to bot users |
| **Customize List** | Only the LLMs or Agents you add to the permitted list are accessible to bot users |
When **Allow users to select alternative LLMs** is toggled off, bot users are locked to the bot's configured default model and cannot switch. The same applies to Agents when **Allow users to select alternative Agents** is toggled off.
***
#### Managing LLM Availability
**Step 1: Open the AI Models Section**
1. Navigate to the bot you want to configure.
2. Open **Bot Settings**.
3. Select the **AI Models** section.
**Step 2: Configure LLM Availability**
In the **Manage LLM Availability** card you have three options:
**Option A: Allow all LLMs**
1. Make sure **Allow users to select alternative LLMs** is toggled on.
2. Select **Allow all available LLM**. All platform-enabled models will be accessible to users.
**Option B: Customize the permitted list**
1. Make sure **Allow users to select alternative LLMs** is toggled on.
2. Click **Customize List**.
3. In the **List of Permitted Bots** modal, select the LLMs you want to make available.
4. Save your selection. Only the chosen models will appear in the Quick Model Selector for users.
**Option C: Restrict to default model only**
1. Toggle off **Allow users to select alternative LLMs**. Users will only have access to the bot's configured default model and cannot switch.
{% hint style="info" %}
If you want to switch from a custom list back to allowing all LLMs, click **Allow all available LLM**. A confirmation dialog will appear warning you that your curated list will be cleared. Click **Allow All LLMs** to confirm.
{% endhint %}
***
#### Managing Agent Availability
The **Manage Agent Availability** card works the same way as LLM Availability:
**Option A: Allow all Agents**
1. Make sure **Allow users to select alternative Agents** is toggled on.
2. Select **Allow all available Agents**.
**Option B: Customize the permitted list**
1. Make sure **Allow users to select alternative Agents** is toggled on.
2. Click **Customize List**.
3. In the **List of Permitted Agents** modal, select the Agents you want to make available.
4. Save your selection.
**Option C: Restrict to default agent only**
1. Toggle off **Allow users to select alternative Agents**.
***
#### Configuring the Initial Model
At the top of the AI Models section, the **Configure Initial Model** card lets you set the default LLM that is pre-selected when users open the bot. Click **Change** to choose a different model, or open the model modifiers to adjust settings like temperature and response style.
***
#### Behavior by User Role
The table below summarizes what each role can see and do:
| Capability | Bot Owner / Bot Editor | Bot User |
| --------------------------------------------------------- | ----------------------------------- | ----------------------------------- |
| **Access Bot Settings: AI Models** | Yes | No |
| **Toggle LLM / Agent availability** | Yes | No |
| **Edit the permitted list** | Yes | No |
| **Quick Model Selector (all allowed)** | All platform-enabled models visible | All platform-enabled models visible |
| **Quick Model Selector (custom list)** | Only permitted models visible | Only permitted models visible |
| **Quick Model Selector (alternative selection disabled)** | Default model only | Default model only |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.blockbrain.ai/for-builders/manage-bot-access/ai-model-and-agents-availability-control.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
