> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/infobridge-wb-matrix-only/8.-manage-bridges.md).
# 8. Manage Bridges
A visual can be added as a source in multiple bridges. The **Manage** option in the InfoBridge tab enables the user to view and manage them.
In the example below, the visual is added in three bridges. You can see the details for each bridge, including the date and time the visual was added as a source, as well as a list of all sources available in the bridge.
Manage Bridges
You can also create a new bridge from here using the **Create Bridge** option. To edit or remove the report from a particular bridge, click **Edit** beside the bridge name. You will be navigated to the respective bridge interface where you can transform, edit or delete it.
Edit report in the bridge
In the next section, we will explore the bridge interface.
---
# 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.inforiver.com/infobridge-wb-matrix-only/8.-manage-bridges.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.
