The context of one meeting is scattered across five screens
A salesperson preparing for a meeting rereads three HubSpot records, two mail threads and a note taken six months ago by a colleague who has since left. The information exists, it is even tidily filed, and piecing it back together eats half the preparation time.
This is the use case where an AI plugged into the CRM genuinely changes something. It is also the one where the question of scope turns political, because a sales book is not a document library: it belongs to someone.
The record follows its owner
Every HubSpot record carries an owner. The connector treats that owner as the read permission: it resolves them to a person in your organisation, then files the record under that person's department. An AI working for someone in sales reaches the sales department's records, and not another department's.
When a record has no owner, or when its owner is a queue, a team, or a person your organisation does not know, it is filed nowhere and waits for an administrator. That is the case for records imported in bulk, and there are always more of those than anyone expects.
A book handover propagates by itself. When a salesperson leaves and their records pass to a colleague in another department, the change of owner brings those records back up on the following pass, and they are refiled under the new department. The previous one loses access at the same moment.
The four records read, and what HubSpot keeps
The CRM is the source everyone is tempted to take whole. Here is what the connector takes, and what it leaves.
A CRM is made of contact details, and we will not pretend to mask them. What protects a contact record is not redaction, it is the fact that only its owner's department can read it.
An email logged in the CRM is company mail
Emails, calls, notes and meetings logged against a record are read like the rest. This is not an exception to the caution applied to mailboxes: an email a salesperson deliberately attached to a client record is an act of record-keeping, and its content is company knowledge by construction.
That same salesperson's mailbox follows a different and far stricter rule, because it holds their life. The Gmail page explains that sorting, which discards private mail before anything is written.
This is not a copy of your CRM
Your Kastel does not replicate HubSpot. From each record it keeps a readable projection, built from a fixed set of standard properties, and that projection alone is what gets written. The full API response is never kept.
That mechanism has a direct consequence, and it is the most useful limit on this page: the properties you created yourselves are not taken in. The “propensity score” field your team added last year does not come in, and a connected AI will not know it.
Nothing travels back to HubSpot either. No record is created, edited or enriched, and the connector asks HubSpot for no write permission. Your CRM stays the system of record, and your Kastel is a reader of it.
What this connector does not do
It does not inherit the full precision of HubSpot's permissions. HubSpot can restrict a record by team and by role; the connector uses the owner only. A finely divided sales organisation will therefore get a coarser scope than its CRM has, coarser in the direction of the department and never in the direction of openness.
It does not know your custom fields, and those are often where your sales method actually lives. Bringing them in is possible, it has not been done, and we would rather write that here than let you discover it on the first try.
Connecting is an administrator's gesture, with a key created in your HubSpot account settings. The connection also refuses to install itself if the account it finds is not the one you declared, which prevents connecting another group entity's CRM by mistake.
See what Kastel does with your commercial knowledge.
The product page shows the whole mechanism, and in particular how one question gets two different answers depending on who asks it, because the two do not read the same records.
See the product
