Connections

A connection is a data source Vistazo can read. Every source is served over MCP, an open standard for connecting software to agents. The built-in assistant reads each server's own tool descriptions and works out from them what a source offers.

Connections live under Settings → Connections, in three groups. Connected holds the sources you have connected. Included holds the five public sources Vistazo hosts (Curated sources). External holds Custom and a directory of common servers.

You connect each source yourself, with your own sign-in or key, and Vistazo holds no shared account. A dashboard's scheduled refresh runs on its owner's connections. A refresh you start runs on yours.

When a chart needs a source you haven't connected, it says so, as in "Stripe isn't connected". A dashboard with no data loaded for that reason offers Connect sources.

External lists servers ready to connect: Salesforce, HubSpot, Stripe, Linear, Notion, Jira / Confluence, Google Sheets, BigQuery, Snowflake, Databricks, Microsoft (Power BI, Fabric), GitHub, Datadog, Supabase, MongoDB, Elasticsearch and dbt. Each vendor hosts its own server, except Google Sheets, which Vistazo runs.

Where a server's address depends on your account, the entry asks for the details it needs and builds the address. Snowflake asks for an account identifier, and Databricks for a workspace URL. Salesforce and Snowflake are set up once for the workspace by an admin. Until then an admin sees Set up and a member sees Request, which asks an admin to do it.

Pick Custom and paste the server's URL. Any remote MCP server works, as long as its address is public HTTPS.

The first row under Connected is always Vistazo. It is Vistazo's own MCP server, the one your agent connects to, and it can't be removed. Its menu has Copy URL, which copies the address, and Configure agent, which opens Settings → Agents with ready-to-copy setup for each agent. Your agent reaches every connection through that one server. See Vistazo as an MCP server.

BigQuery asks for nothing before you sign in with Google. Vistazo then lists the Google Cloud projects your account can see and checks which ones you can run queries in.

The billing project is the one your queries run in and are billed to. If one project qualifies, it is chosen for you. If several do, the connection asks you to pick one and runs no queries until you do. A project you can't pick needs the BigQuery Job User role, or the BigQuery API turned on, from whoever owns it.

Your billing project is yours alone in that workspace, and the assistant runs every query there. Change it with Edit settings on the connection. After you create a new project, Refresh tools reads the list again.

Google Sheets signs in with your Google account and only reads. It opens any spreadsheet you can open, but it can't list or search your files, so give the assistant the sheet's URL. It never changes a sheet, and it always signs in with Vistazo's own Google app.

Connect it twice to reach two Google accounts, such as work and personal. The assistant knows which account each connection signed in as, and tries the other when one can't open a sheet.

GitHub signs in through Vistazo's GitHub app, which only reads. It sees only the repositories you choose for it. The first time you connect, GitHub asks where to install the app (your account or an organization) and which repositories it can read, then brings you back to Vistazo.

To add or remove repositories later, open the app's install page and pick the account. You don't need to reconnect. An organization that restricts GitHub apps needs an owner to approve Vistazo before its repositories appear.

Microsoft connects Power BI and Fabric warehouses and lakehouses. Pick one under Product. Sign in with your work or school Microsoft account. A personal Microsoft account can't reach either.

Power BI reads semantic models and reports, and runs DAX queries against them. It only reads. Every query runs as you, so your own Power BI permissions and row-level security apply. Data is as fresh as the semantic model's last refresh in Power BI. It doesn't reach Power BI dashboards, paginated reports or apps.

A Fabric warehouse or lakehouse is set up once for the workspace by an admin, who signs in with Microsoft, picks it from the list and saves it. Members then connect to it with their own Microsoft sign-in. It reaches the warehouse's or lakehouse's tables and views and runs SQL queries against them, each as the member, so their own Fabric permissions apply. Fabric returns long text values cut to 4,000 characters.

Azure SQL Database, Azure Synapse and Azure SQL Managed Instance are available on request. The Vistazo team can enable them for your workspace within 24–48 hours.

Until Microsoft verifies Vistazo, an admin in your company's Microsoft Entra approves Vistazo once. Nobody in the company can connect before that. When the sign-in window is refused for this reason, the connection's page shows a link to send your Microsoft admin, who approves Vistazo with it. If your browser blocks pop-ups, the sign-in takes over the page instead and no link appears; allow pop-ups for Vistazo and connect again.

Power BI connects only when your company's Microsoft home region supports all Fabric workloads. Power BI-only regions and sovereign clouds aren't supported.

Vistazo uses whatever the server supports.

A key doesn't renew itself, so when the server stops accepting it the connection asks for a new one. Tokens and keys are encrypted and held on Vistazo's servers, where the browser can't read them.

Open a connection to see the tools it offers. Its menu holds the actions that apply to it.

A hosted source has nothing to sign in to, so you disconnect it rather than disable it. Adding it back from Included is one click.

When the last person disconnects a server Vistazo doesn't host, its instructions are deleted. It also leaves the workspace's list, unless a dashboard or notebook still uses it.

Each tool on a connection is Allowed, Ask first or Blocked. The connection's page lists every tool by permission, and you can change any of them.

A tool Vistazo classifies as read-only starts as Allowed, so the assistant calls it whenever it needs the data. Anything else, such as creating an issue or updating a record, starts at Ask first. The assistant can see that tool, but before calling it, it asks in the thread and names what it is about to do. You can allow it always, allow it once, or decline. Allowing it always sets it to Allowed, and declining sets it to Blocked.

Your choices are your own, in that workspace. Your Allowed never widens what a colleague's assistant can do. Refreshing the tool list keeps your choices, except that an Allowed write tool whose definition changed goes back to Ask first.

Outside a chat there is nobody to ask. Your agent runs only Allowed tools. A widget's scheduled refresh still runs the tool wired into it when that tool is set to Ask first. Wiring the tool into the widget counts as your approval to run it on the schedule. Nothing ever runs a Blocked tool. The hosted sources are read-only, so their tools start Allowed. A view-only member's assistant gets a connection's read-only tools and nothing else.

A connection in trouble shows on the widgets that depend on it.

In Settings → Connections, connections in trouble sort to the top. Their status is a button that reconnects.