> For the complete documentation index, see [llms.txt](https://help.reekolect.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.reekolect.ai/reekolect-resource-center/how-reekolect-works/bot-management/bot-settings/website-bot-settings/user-access.md).

# User Access

This page contains information on how you can decide who can access your bot.

## Bot Availability Settings

Customize the availability control settings to manage device support, IP address blocking, page visibility, and country access:

<table><thead><tr><th width="279">Setting</th><th>Description</th></tr></thead><tbody><tr><td>Device Support</td><td>Determine which types of devices can access the bot.</td></tr><tr><td>Block IP Addresses</td><td>Enter specific IP addresses to block or restrict access to the bot.</td></tr><tr><td>Hide Chatbot on Specific Pages</td><td>Enter URLs of pages where you don't want the bot to appear.</td></tr><tr><td>Select Countries to Enable Bot</td><td>Choose the countries where you want users to access the bot.</td></tr></tbody></table>

#### Note

These settings allow you to control the bot's accessibility based on device types, IP addresses, specific web pages, and user locations.

**Saving Changes**

Once you have configured all the settings according to your requirements, click the "Save Changes" button to apply the changes. The bot will update its setting after some time ones cache is removed.

{% hint style="info" %}
Use `Invalidate Cache` option to make changes live right away.
{% endhint %}


---

# 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://help.reekolect.ai/reekolect-resource-center/how-reekolect-works/bot-management/bot-settings/website-bot-settings/user-access.md?ask=<question>&goal=<user_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.