What data AI should be allowed to see, and what it shouldn't
More access makes it more useful and more dangerous, and both are true at once. Sort your data into rings, give each tool the smallest ring that does its job, and widen one ring at a time with the reason written down.

Both halves of the question are true
An assistant that can see your price list, your procedures and your last 100 proposals writes a better proposal than one that can't. That's real. It's also true that the same assistant, if it can see payroll, will one day put a salary into a document for someone who shouldn't see it – not out of malice, but because it was asked a question and that was the most helpful answer it had. So the question isn't whether to give access. It's how to give the useful part without the dangerous part, and the way to do that is to stop thinking about "the data" as one thing.
The four rings
| Ring | What's in it | Default for tools |
|---|---|---|
| Public | The website, brochures, published price lists, anything a customer could already see. | Any tool can read it. |
| Internal | Procedures, templates, meeting notes, product information – the things a new starter gets shown in week one. | Any tool can read it. This is where most of the usefulness lives. |
| Confidential | Customer records, the pipeline, contracts, supplier terms, margins by job. | Read for a named job, with a named owner and a log. Write only after a review. |
| Restricted | Payroll, staff personal data, the management accounts, legal matters, anything under a non-disclosure agreement. | Not available to agents. A person can use an assistant on it inside a company-owned workspace with training switched off, for a named task. |
Most businesses find the internal ring is bigger than they thought and the confidential ring smaller. In our experience the useful work is mostly in the first two rings, and the worry is mostly about the fourth.
The smallest ring that does the job
Give each tool the smallest ring that does its job. A meeting-notes agent needs the internal ring. A quoting agent needs the price list and the customer's record, which is a slice of the confidential ring, not the whole thing. Nothing needs the restricted ring to do a sales or operations job. When a new job needs more, the owner asks, the reason gets written down, and the ring gets widened for that one tool.
This works because it's specific. "Be careful with sensitive data" isn't really a rule, because nobody can check it. "The quoting agent may read company records and the price list, and may write to the quote field only" is one.
A personal assistant is a different case
A person's own assistant sees whatever that person can see. There's no sensible way to give it less. So the controls there are different: the company owns the workspace, the provider doesn't train on your data, history is kept on your terms, and the person has a plain rule about what never goes in. Protecting IP and company data covers those settings. Agents, which run on their own, are where the rings apply.
The two controls that matter more than the rings
Access gets granted, not copied. Nobody pastes an export of the CRM into a tool. The person who administers the system grants the tool a connection, and that connection can be removed in one place. And read comes before write – a tool earns the right to change a record by reading for a month without surprising anyone.