Breeze AI assistant: Add granular permissions for assistant actions (read, write, delete)

Status: Idea Submitted

Right now the Breeze AI assistant’s access is a single on/off setting which does not make it very usable. We need more granular control over what the assistant can do, with separate permissions for reading records, creating or updating records, and other actions such as deleting or bulk editing.

The assistant inherits permissions from the user, but that is not sufficient on its own. A user having bulk edit access is fine when they make those changes deliberately in the UI. It is a different level of risk when the assistant can make the same bulk changes from a prompt, where a misunderstood request could update or overwrite a large number of records at once.

Suggested controls:

  • Separate toggles for read, create/update, delete.
  • The ability to set these per team or per permission set.

This would let admins enable the assistant for research and summarization across the portal while keeping tighter control over changes to CRM data.

Either malicious or unintentional actors have the same power to make potentially catastophic changes to data structure or elements. As presently constructed, Breeze is far too powerful to allow users access. It’s very scary.

It would be ideal to tie edit capabilities within Breeze to roles in HubSpot.

This is absolutely essential. Ideally, we should be able to set Breeze to read-only.