Synquil vs. built-in AI connectors

The connectors built into Claude and ChatGPT inherit each person's existing permissions in the tool being connected: if someone can already open a file or record in the source system, their AI can read it, and if they cannot, it cannot. That is a sound default, and for a company whose tools are already locked down person by person, it may be all you need. It also means your AI access is exactly as granular as your messiest source tool — and for most small companies, the shared spreadsheet everyone can open is not granular at all.

Synquil holds one synced copy of your data instead of passing questions through to each tool, so access is defined once, over that copy, down to individual columns — and every question anyone's AI asks lands in a single log.

Synquil
Built-in AI connectors
Where access is decided
Once, in Synquil, across every connected source — one place to answer "what can this person see?"
Separately in each source tool. Access to a HubSpot connector is whatever that person has in HubSpot.
How precise it can be
A source, a table, or specific columns within a table. Share the deal without the margin.
As precise as the source tool's own permissions are. If everyone can open the spreadsheet, everyone's AI can read all of it.
What an ungranted person sees
Nothing — ungranted tables are not listed and cannot be named. The data is invisible, not refused.
Whatever the source tool shows them, which for a shared file or workspace is usually everything in it.
Admin control over connectors
Available on the Team plan: roles, per-column grants, and an audit log.
Organization-wide connector and tool controls on Team and Enterprise; role-based per-connector permissions on Enterprise only.
Cross-source questions
Native — one schema, so a question can span HubSpot, Stripe, and your spreadsheets at once.
Each connector answers for its own tool. Joining them means asking separately and reconciling by hand.
Audit trail
One append-only log across every source: who asked, which tables, how many rows, including blocked attempts.
Per-tool logging where the source tool provides it. No single view across sources.
When someone leaves
Remove them from the workspace and access ends within one request, across every source at once.
Revoke their account in each source tool, or in your identity provider if the connectors are provisioned through one.

Where built-in connectors are the better fit

If your source tools already enforce exactly the per-person access you want, built-in connectors give you that for free: nothing to configure, nothing to keep in step, and no second system to maintain. They also read the live state of a tool at query time, with no sync schedule in between. The trade-off shows up when the permissions you want do not exist in the source — sharing three columns of a spreadsheet rather than the whole file — when you want one place to see and change who can see what, when a question needs data from more than one tool at once, or when you need a single record of what your team's AI has been asking.

Accuracy note

Connector behaviour and plan availability are described as documented by the AI vendors at the time of writing and change often. Check their current documentation before making a decision, and tell us if anything here has gone out of date.

Related reading

Give your team AI access to company data. Not to all of it.

Get started free