> For the complete documentation index, see [llms.txt](https://docs.ixhello.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ixhello.com/ixhc/general/manage-bot-visibility.md).
# Manage Bot Visibility
This section explains the restrictions applied to bots using classified or private connections, designed to enhance security and comply with Security Assessment and Recommendations (SAR) and HRIX processes.
1. Feature Overview:
1. Bots using private connections have restrictions on public access and conversation history.
2. Alerts are provided to inform users on UI, when certain features are disabled due to private integrations.
2. Purpose:
1. These restrictions aim to mitigate the risk of unauthorized data exposure, also known as bot exfiltration.
3. Management:
1. Governance of private connections involves internal oversight to ensure security compliance.
2. Infrastructure management is responsible for maintaining these restrictions.
4. Current Scope:
1. These measures apply to internal users only but may be adapted for external requirements as needed.
5. Prerequisites :
1. The bot must be integrated with classified or private connections recognized by the system.
2. The system infrastructure must be configured to identify and manage these private connections.
3. Users must have access to the latest system updates to ensure compliance with these restrictions.
4. Applicable for any organization which has enhanced security requirements and want to restrict bot visibility for apps that have private data connection.
### Impact
1. If any assistant is using a private connection, option to “grant public access” will be disabled, along with the reason and name of private connection.
1. Click on “manage” for any available assistant:
b. Option enabled in assistant settings when private connection is not used:
2. Any assistant, if using a private connection, will be restricted from enabling call/text option with appropriate error message:
a. Error message displayed when user clicks on “Activate”:
3\. For assistants with private connections, the conversation history will not be displayed or stored.
a. Open “chat history” for assistant with private connection:
b. For the selected bot, click on “submit”:
c. Error messages will be displayed:
4. In Studio mode, Lex publishing is restricted for assistants with private connections.
a. Open assistant with private connection under custom apps:
b. Click on “Add app publishing” with Lex channel:
c. Save button will be disabled with reason and name of private connection mentioned:
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ixhello.com/ixhc/general/manage-bot-visibility.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.