← All articles

AI Leadership

What Data Access Does an AI Agent Actually Need?

Use a task-to-permission matrix to give an AI agent bounded access, separate drafts from sends, and test denied actions before release.

By , Co-Founder & CEO4 min read
One document passes through a narrow gate into a larger compartmented archive.

Your agent needs to prepare a weekly account summary. The setup screen asks for access to the CRM, email, calendar, and billing system. Approving all four is convenient for the installer. It also gives the agent capabilities the summary may never need.

Start with the finished business action. If a manager needs a summary draft, define the records the agent must read and the place it may save that draft. Then decide which capabilities stay with the manager.

A permission matrix for one account-summary task

Consider this hypothetical workflow: an account manager requests a summary for one assigned client. The agent gathers recent CRM notes and open support issues, prepares a document, and leaves the manager to review it. The following matrix is an original design example.

Task stepAllowed accessDenied action
Read account activityRead notes for the requested account within the agreed date range.Read unrelated accounts or export the entire CRM.
Read open support workRead ticket status and approved summary fields for that client.Close tickets, alter priority, or copy restricted attachments.
Prepare the summaryCreate one draft in the manager's review folder.Overwrite source records or another manager's documents.
Deliver the draftNotify the assigned manager that a draft is ready.Email the client, invite outside users, or change sharing permissions.

The account manager gains a useful draft without surrendering the decision to send it. If the team later wants client delivery, treat that as a new approved action with its own recipient and content checks.

Enforce the boundary outside the prompt

Put the matrix in the agent's instructions, but ask the builder how the systems enforce it. A sentence telling an agent to ignore other accounts cannot replace a permission check on the data request.

The builder should show which identity makes each request, which records that identity can access, and which tool exposes the write action. If a connector offers account-wide access, ask whether a smaller service identity, a filtered intermediary, or a restricted view can support the task. Some products will not support the boundary you need; that is a platform constraint to resolve before release.

Separate create, update, delete, and send capabilities in the design review. A tool that can save a new draft need not delete old documents. A tool that reads email need not send messages. Keep secrets in the connection mechanism rather than in the article, prompt, or generated report.

Test the permissions with a curious operator

Have a reviewer request a summary for an account outside their assignment. The system should refuse the access or route the request to an authorized person. It should not retrieve the information and ask the reviewer to behave.

Next, put an instruction inside a test CRM note that tells the agent to send its report to an outside address. Treat that note as task data. Confirm that the agent lacks the delivery capability or that the delivery approval rejects the recipient.

Finally, revoke the connection while a draft is in progress. Confirm that the agent reports the missing access and leaves a recognizable incomplete state. A polished report assembled from partial records can mislead the manager.

Record the requested account, tool identity, accessed sources, created draft, and any denied action. The operator needs enough evidence to explain what happened without turning the log into a second unrestricted customer database.

Name the person who can expand access

Use a short change request: new task, new records, new action, business reason, approving owner, and test. Expanding access because one run failed bypasses that decision.

NIST's voluntary generative AI profile provides a broader risk-management reference; the matrix here is our practical task design. For leadership ownership, read who owns AI decisions. The Ops Guide's fractional CAIO service can help you turn an agreed task into explicit operating decisions.

Luke Thompson

About the author

Luke Thompson

Co-Founder & CEO, The Ops Guide

Luke Thompson is Co-Founder and CEO of The Ops Guide. He writes about practical uses of AI, workflow automation, custom software, and SEO for growing businesses.

About The Ops Guide

The Ops Guide helps businesses improve how work gets done through custom software, workflow automation, AI systems, and SEO services.

The Ops Guide Brief

Get AI news you can use.

The developments worth your attention, what they change at work, and what to do next. Choose a daily briefing or a weekly selection.

Free to subscribe. Confirm by email. Unsubscribe any time.