Treat the connection file as a secret
The API address and token provide access within the current Bridge permissions. Store the file locally, share it privately and exclude it from Git. A subscription key and a connection token serve different purposes; normal agent work does not require the server administrator password.
Permissions are checked on each request
Bridge controls visible databases and permitted operations. Web chat also requires explicit write permission for a task, with a separate option for configuration changes. Agent instructions cannot expand permissions or change the selected database.
Understand the service dependencies
External access passes through the secure BAS Bridge gateway and the application running on your server. Availability depends on both ends and the network. Stopping the application ends access through it. This does not disable independent HTTP services that your company published separately.
Control data and outcomes
The hosted AI uses the configured server-side provider and receives data needed for the task. Choose permissions and tasks according to your company rules. Review statuses, errors and usage in your workspace; if a write outcome is uncertain, verify the actual state before retrying.
Ready to connect your database?
Open your workspace or download Bridge with your access key.