Security & sovereignty

AI agent permissions: a matrix for sales, support and finance

Set AI agent permissions one business decision at a time. A salesperson preparing a quote, a support officer answering a delivery question and a bookkeeper matching an invoice each need different records. Give each job its own row in an access matrix and test the result under the identity the agent will actually use.

red padlock on black computer keyboard
Photo by FlyD on Unsplash

Part of our guide to Sovereign AI in Australia: a practical guide for operators

On this page · 6 sections
  1. Start with a verb and a business record
  2. Adapt this access matrix to your own roles
  3. Confirm whose identity the connected tool uses
  4. Rehearse a mismatch before enabling a write
  5. Give a second operator the evidence
  6. Frequently asked questions

Take a recent job that finished successfully and reconstruct what the operator needed. For a quote follow-up, they may have read a contact, opened the accepted estimate and drafted a reminder. They may also have had access to the whole sales pipeline through their personal account. The completed job gives you evidence for the first three capabilities. Access inherited from the operator's seniority needs its own justification before it is given to a service.

Start with a verb and a business record

Write the job as a sentence that a manager can inspect. “Prepare a callback note for the account owner using the open enquiry and its latest quote” gives the administrator an object, an action and a destination. “Help sales” leaves all three open. Add the part the assistant should return when an input is missing. For the callback note, a useful return might be the enquiry reference and a question asking which of two similarly named companies owns it.

Identify the person who can define each boundary. The sales manager might own the meaning of a quote stage while the system administrator controls the connector. Ask them to fill in their parts together. When a connector supports a broader permission than the manager intended, record the difference. A broader grant is a purchasing and process decision that deserves to be visible to the person accepting it.

Adapt this access matrix to your own roles

JobRecords the agent can readWork it can prepareDecision held by a person
Sales follow-upAssigned enquiry, named account and current quoteA draft callback note identifying the quote revision and next questionAccount owner approves the recipient, wording and send
Support requestAssigned ticket and verified order statusA draft reply giving the latest event and its source timeSupport lead approves a change of address, refund or replacement
Invoice matchingInvoice, related purchase order and delivery receiptA proposed match showing the amount and any discrepancyFinance officer resolves mismatches and releases any payment through the usual process

Copy the rows that match the trial and replace each role with a named owner. On the sales row, specify whether the assistant may open other opportunities owned by the same customer. On the support row, define who verifies the relationship between the person making the enquiry and the order. On the finance row, identify where the purchase order and delivery receipt come from and which version can be used.

Add the destination for each draft. A note saved to a private review queue has a different audience from an activity displayed on a customer portal. Ask the reviewer to open the result as an ordinary colleague and confirm who else can see it. A carefully restricted source loses much of its protection if the summary is published to a wider audience by default.

Confirm whose identity the connected tool uses

A manager can approve a sensible matrix while an integration quietly uses the identity of the administrator who installed it. Ask the person setting up the connection to show the service, user or application identity that will run the ordinary job. Record its owner and how to inspect its grants. Keep credentials out of the matrix. The team needs to know where permissions are managed and who can change them.

Provider terminology matters here. Microsoft distinguishes an app acting for a signed-in user from an app using its own identity. Under delegated access, both the granted permissions and the user's own access affect what the app can do. An application permission can reach associated resources without the person signing in. Look at the actual permission type when someone describes a connector merely as “read access”. Microsoft Graph permissions overview.

Google recommends requesting the smallest applicable scopes when the feature that needs them is used. In a buying trial, ask the supplier to identify which of your intended tasks requires each requested permission. Then repeat an ordinary task after declining an optional grant. Record whether staff can still complete the useful part of the job and what the application explains when the missing feature is requested. Google OAuth best practices.

Rehearse a mismatch before enabling a write

Create a fictional purchase order for six cartons and a delivery receipt for four. Give the assistant the matching invoice for six. The bookkeeper should receive a proposed match showing the short delivery and the source of each quantity. Ask the bookkeeper to open the evidence using their ordinary account. A useful finance trial can end at that desk, with the payment system completely outside the assistant's access.

Next choose an invoice from a second test supplier with a similar name and no related order. The evidence should lead to an unresolved item. Have the reviewer inspect the draft queue, both supplier records and the downstream accounting system. You want to know where an entry actually landed and whether either balance changed. Checking the destination independently is how a business owner can verify the boundary written in the matrix.

Test a late change as well. Suppose the receiving clerk corrects the delivery receipt after the assistant has prepared its summary. The reviewer should be able to identify the source revision used and refresh the comparison before making a decision. An approval belonging to an earlier draft should not silently authorise a changed amount. Record who reviewed the corrected position and which version was accepted.

Give a second operator the evidence

Choose a colleague who covers the desk during leave and give them one approved draft and one unresolved item. Ask them to find the source records, identify the person who can act and explain what has already happened. If they must ring the original reviewer to establish whether money moved or a message was sent, the handover needs a better receipt. The destination reference and time often answer that question without exposing the contents of the whole source document.

In Cortex, Fulcrum Sessions coordinates work across people and specialist agents. When evaluating that model, carry the matrix across the handover. A specialist that prepares the summary and a colleague who commits the decision each need an identifiable role. Have the team demonstrate the connection and action available in your own setup, including what happens when the intended reviewer is away.

Reopen a row when the business changes the job, the connector or the destination audience. Review an example with the people who actually use it. Sometimes the simplest improvement is to remove an unused action or to give the reviewer a better link to the evidence. Keep the previous decision alongside the new one so the next administrator can explain why a permission exists.

Related guides: Sovereign AI in Australia: a practical guide for operators · Least privilege for AI agents: give each one only the access its job needs · Audit trails for AI agents: what to record for every action.

Frequently asked questions

How many rows should we write for the first trial?

Start with one recurring decision and the people who prepare and approve it. Add a row when the source, destination or consequence changes enough that a different person would need to accept the risk.

Can two departments share one agent account?

First check whether each job can be restricted independently and attributed to its operator. If the shared identity combines access that neither job requires on its own, separate connections can make the boundary easier to enforce and review.

Who should approve a new permission?

Ask the owner of the affected business record to decide whether the access is justified and the administrator to verify what the grant allows. Save the business reason, test result and owner with the row so someone can reassess it when the job changes.

Sources

  1. Microsoft Graph permissions overview
  2. Google OAuth best practices

General information only, not legal, financial or professional advice. Check the source for your circumstances.