AI Agent Permission Design: Least Privilege, Human Approval, Logs, and a Stop Plan for Each Job

Project & Development

AI Agent Permission Design: Least Privilege, Human Approval, Logs, and a Stop Plan for Each Job

Advanced | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)

Advanced: Assumes you know the technical terms and methods, and the steps are only outlined. Work through it on your own, guided by decision criteria and points to check.

A permission design template for deciding, job by job, the least access to give AI agents and automation tools, which actions a person approves, what to log, and how to stop them. Common traps: test-time permissions left on, personal accounts used for agents, and read emails or documents treated as instructions. Treat outside content as read-only data and require human approval before sending, deleting, or paying; draw that line by impact and reversibility. Start by copying connected apps and their permissions from your admin screen, then write how to cut the gap. Log who did what and when with 5W1H, and review on a set cycle and when tools change or you delegate more jobs. In Japan, IPA's Top 10 Information Security Threats 2026 (organizations) newly listed AI-related cyber risks at third place; check the latest guidance. Four whiteboard pages (jobs, permissions, approval, log and stop) plus a five-column task board of four parent tasks with three subtasks each.

0 Likes 0 Copies Author: WeProcess
AI agents permission design least privilege information security business automation
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Read the whiteboard text as plain text

Permission Design for AI Agents and Automation Tools

How to use (4 pages): ① Write the purpose and list jobs, tools, and data on page 1 (boards①–⑤) → ② Minimize permissions and check pitfalls on page 2 (boards⑥–⑨) → ③ Plot actions on two axes and draw the approval line on page 3 (boards⑩⑪) → ④ Decide logs, stop steps, and reviews on page 4 (boards⑫–⑭)

1/4 List the jobs to hand over

① Purpose and scope (start here)

  • Purpose e.g. hand over drafting replies to inquiry emails and halve the time to reply
  • Scope and period e.g. support department email only. A trial for the first month
  • Accountable manager and contact e.g. the support manager is accountable. Permission questions go to the IT contact

② Jobs to hand over, with tool, data, and owner

Job to hand over Tool used Data touched Owner
Job 1 e.g. Summarize inquiry emails and draft replies e.g. AI agent linked to email e.g. Shared inquiry inbox e.g. Support manager
Job 2 e.g. Read invoice PDFs and enter them in accounting software e.g. Automation tool (workflow) e.g. Invoice folder and accounting data e.g. Head of accounting
Job 3 e.g. Save meeting minutes to a shared folder e.g. AI summary in the meeting tool e.g. Meeting recordings and shared folder e.g. General affairs
Job 4 e.g. Send quote replies to customers e.g. Sales-support AI agent e.g. Customer contacts and quotes e.g. Sales director

③ Read-only (just looking at contents)

  • e.g. Read inquiry emails and summarize them
  • e.g. Read amounts from invoice PDFs
  • Mark actions that read received emails or outside documents with ☆ (checked in ⑨)

④ Write (create, change, or delete in-house data)

  • e.g. Create a reply draft (not sent)
  • e.g. Enter a journal entry as a draft in accounting software
  • Mark delete or overwrite actions with ★

⑤ Send outside (reaches outsiders or moves money)

  • e.g. Send an email to a customer
  • e.g. Confirm a payment
  • Actions that land here always get a rule in ⑪

2/4 Draw permissions to grant

⑥ From ② and the split in ③–⑤, cut permissions to the minimum

Permissions needed Current permissions How to cut Account used
Job 1 e.g. View the inbox and create drafts e.g. Read, write, and send on every mailbox e.g. Limit to the inbox and remove sending e.g. Dedicated agent account
Job 2 e.g. View the invoice folder and draft journal entries e.g. Full rights on accounting data (as left after testing) e.g. Remove posting and deletion rights e.g. Dedicated automation account
Job 3 e.g. Write to the minutes folder e.g. Edit rights on the whole shared drive e.g. Limit to the minutes folder e.g. General affairs shared account → dedicated
Job 4 e.g. View quotes and draft replies to send e.g. Can also export customer data e.g. Remove export; send only after approval e.g. Sales rep's personal account → dedicated
Shared connections e.g. Connect only the tools you need e.g. 3 unused connections remain e.g. Remove the unused connections e.g. The admin keeps the list of connections

⑦ Pitfall: strong test-time permissions carried into production

  • What happens: e.g. full permissions granted during testing stay, so a wrong action reaches all the data
  • How to check: e.g. compare the permissions column of connected apps in the admin screen with "Permissions needed" in ⑥
  • How to prevent: e.g. apply the cuts in ⑥ before moving to production, and have the accountable manager confirm
  • Result: e.g. Job 2 applies. Fix by Monday

⑧ Pitfall: letting the agent use a personal account

  • What happens: e.g. it stops when the person moves or leaves, and the log does not show whether a person or the agent acted
  • How to check: e.g. look for personal names in the "Account used" column of ⑥
  • How to prevent: e.g. create a dedicated account for each agent or automation and name its owner
  • Result: e.g. Job 4 applies. Request a dedicated account

⑨ Pitfall: treating what it reads as a person's instruction

  • What happens: e.g. it follows a request written in a received email or document all the way to sending or deleting
  • How to check: e.g. in the tool settings, see whether sending, deleting, or paying can run automatically based on what it read
  • How to prevent: e.g. treat outside content as read-only data and put human approval before sending, deleting, or paying
  • Result: e.g. Job 1 has automatic sending on. Turn it off and require approval

3/4 Draw the approval line

⑩ Line up the actions kept in ⑥ by size of impact × reversibility

Vertical axis: Size of impact (higher = larger) / Horizontal axis: Reversibility (further right = easier to undo)

  • Prohibit, or two approvers Large impact, hard to undo e.g. sending email outside the company, permanently deleting files, confirming payments
  • Human approval Large impact, but can be undone e.g. changing shared-folder permissions, updating customer information
  • Human approval, or automatic within a set range Small impact, but hard to undo e.g. posting in internal chat, contacting fixed recipients
  • Automatic is fine (keep a log) Small impact, and can be undone e.g. summaries, drafts, labeling

⑪ From the placement in ⑩, set each action's rule and approver

Rule (automatic, approval, prohibited) Approver What to check before approving
Drafts and summaries e.g. Automatic (keep a log) e.g. Not needed e.g. Read the log in one batch once a week
Posts inside the company e.g. Automatic only for set channels e.g. Team leader e.g. Whether the channel and recipients are within the set range
Sending outside e.g. Human approval e.g. The person in charge and the accountable manager e.g. Recipient, attachments, source email
Deletion and payment e.g. Prohibited (a person does it) e.g. Head of accounting e.g. Do not give the agent the permission

4/4 Log and be ready to stop

⑫ Records to keep for each action in ⑪ (pitfall: no record of who had the agent do what, and when)

  • Records to keep
    • What Action taken e.g. the action and its target (recipient and subject of the email sent, name of the file deleted)
    • Why Reason e.g. the reason for the request (inquiry number, the message that triggered it)
    • Who People and account e.g. who asked, who approved, and the dedicated account that acted
    • When Times e.g. time of the request, of the approval, and of the run
    • Where Tool and data e.g. the tool used and where the data it touched is stored
    • How Auto or approved e.g. automatic or human approval, and which rule in ⑪ it falls under

⑬ Four steps to stop it when something looks wrong (pitfall: no stop procedure)

  1. Notice Decide the warning signs in advance e.g. an action prohibited in ⑪ appears in the log, or the number of sends is double the usual
  2. Stop Who stops it, and how e.g. the person on duty pauses the run in the automation tool's admin screen
  3. Remove Remove permissions and connections e.g. remove the dedicated account's connection in the admin screen and disable the keys used to connect (API keys and access tokens)
  4. Check and restore Check the impact in the ⑫ log e.g. list the emails sent and data changed, tell those involved, and restore

⑭ Review cycle and triggers

  • Regular review e.g. every 3 months, review the permissions in ⑥ and the rules in ⑪
  • Review triggers e.g. a tool update, more jobs handed over, a staff move, or a stop in ⑬
  • Who reviews and how to check e.g. the IT contact and each owner. Pull one week of the ⑫ log and read it

Task board contents

Not started 16 items

List delegated jobs

On page 1, write why you are bringing in AI agents or automation tools, then tabulate each job you hand over with its tool, data, and owner, and sort the actions into read-only, write, and send outside. This list of jobs is what you cut permissions for from page 2 on. Press Ctrl+F (⌘F on Mac) and type '3/4' to jump to page 3.

Open connected apps

Do not remove any connection yet; just copy. Open the admin screen of your email or file-sharing service (for personal use, the list of connected apps in your account settings; screen names differ by service, so check your service's help). Write the AI agents and automation tools you find into the 'Tool used' column of board ② and the permissions they hold (read, write, send) into the 'Current permissions' column of board ⑥ (put unused connections in the 'Shared connections' row of ⑥). Done when names and permissions are written.

Set purpose & scope

On board ①, write the purpose, the scope and period, and the accountable manager and contact for questions. Done when the three notes are filled and the manager's name is in.

Sort into 3 frames

Sort each job's actions on board ② into boards ③ read-only, ④ write, and ⑤ send outside. Mark delete or overwrite actions with ★ and actions that read received emails or outside documents with ☆. Draw the approval line for every action in ⑤ on page 3.

Draw permissions

On page 2, compare the permissions each job in ② needs with what it has now, decide how to cut them, and check the three pitfalls. Excess permissions decide how far the damage of a wrong action spreads, so spend the most time on this parent task.

Compare permissions

In the table on board ⑥, write each job's needed permissions, current permissions, and account used. Copy current permissions exactly as the admin screen shows them. Done when the 5 rows are filled.

Decide how to cut

In the 'How to cut' column of ⑥, write the permissions to remove and the scope to narrow, and get confirmation from the owner and the accountable manager. Once confirmed, move the card on from the 'Awaiting manager's OK' column.

Check 3 pitfalls

For each pitfall on boards ⑦–⑨, write what happens, how to check, the move that prevents it, and the result. Write a fix deadline in the result for any that apply.

Draw approval line

On page 3, line up the actions kept in ⑥ by size of impact and reversibility, then set each action to automatic, human approval, or prohibited, with an approver. These lines are the premise for the logs and stop steps on page 4.

Plot on two axes

Place the actions kept in ⑥ in the four areas of board ⑩. When unsure, put an action on the side with larger impact and harder to undo.

Assign approvers

In the table on board ⑪, write each action's rule (automatic, human approval, prohibited), the approver, and what to check before approving. Done when every outside-sending action is approval or prohibited.

Apply to settings

Apply the rules in ⑪ in each tool's settings as approval steps or by adding and removing permissions. For actions where the settings cannot require approval, remove the permission and have a person do it.

Log and stop

On page 4, decide the log items with 5W1H, plus the four stop steps for when something looks wrong and the review cycle. After you start using it, track this parent task in the 'To next review' column.

Decide what to log

Following the six questions on board ⑫, write the items to keep in the log. Also check on each tool's log screen that those items are really recorded.

Set the stop steps

For each of the four steps on board ⑬, write the owner and the screen to use. Done when the on-duty person's name and contact are in and shared with those involved.

Set review dates

On board ⑭, write the regular review cycle, the triggers, and who reviews. Done when you put the first review date in the calendar.

Writing it down 0 items

Awaiting manager's OK 0 items

Applied to settings 0 items

To next review 0 items

← Back to templates

Preview mode AI Agent Permission Design: Least Privilege, Human Approval, Logs, and a Stop Plan for Each Job

Whiteboard preview

① Purpose and scope (start here) ② Jobs to hand over, with tool, data,... ③ Read-only (just looking at contents) ④ Write (create, change, or delete in... ⑤ Send outside (reaches outsiders or ... ⑥ From ② and the split in ③–⑤, cut pe... ⑦ Pitfall: strong test-time permissio... ⑧ Pitfall: letting the agent use a pe... ⑨ Pitfall: treating what it reads as ... ⑩ Line up the actions kept in ⑥ by si... Prohibit, or two approvers Human approval Human approval, or automatic within a... Automatic is fine (keep a log) ⑪ From the placement in ⑩, set each a... ⑬ Four steps to stop it when somethin... ⑭ Review cycle and triggers Permission Design... How to use (4 pag... Purpose and jobs ... Decisions and per... Pitfalls and high... Logs and reviews 1/4 List the jobs to ... Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Draw permissions ... ↙ 3/4 Purposee.g. hand over drafting replies to inquiry emails and halve the time to reply Scope and periode.g. support department email only. A trial for the first month Accountable manager and contacte.g. the support manager is accountable. Permission questions go to the IT contact Job to hand over Tool used Data touched Owner Job 1 e.g. Summarize inquiry emails and draft replies e.g. AI agent linked to email e.g. Shared inquiry inbox e.g. Support manager Job 2 e.g. Read invoice PDFs and enter them in accounting software e.g. Automation tool (workflow) e.g. Invoice folder and accounting data e.g. Head of accounting Job 3 e.g. Save meeting minutes to a shared folder e.g. AI summary in the meeting tool e.g. Meeting recordings and shared folder e.g. General affairs Job 4 e.g. Send quote replies to customers e.g. Sales-support AI agent e.g. Customer contacts and quotes e.g. Sales director e.g. Read inquiry emails and summarize them e.g. Read amounts from invoice PDFs Mark actions that read received emails or outside documents with ☆ (checked in ⑨) e.g. Create a reply draft (not sent) e.g. Enter a journal entry as a draft in accounting software Mark delete or overwrite actions with ★ e.g. Send an email to a customer e.g. Confirm a payment Actions that land here always get a rule in ⑪ Permissions needed Current permissions How to cut Account used Job 1 e.g. View the inbox and create drafts e.g. Read, write, and send on every mailbox e.g. Limit to the inbox and remove sending e.g. Dedicated agent account Job 2 e.g. View the invoice folder and draft journal entries e.g. Full rights on accounting data (as left after testing) e.g. Remove posting and deletion rights e.g. Dedicated automation account Job 3 e.g. Write to the minutes folder e.g. Edit rights on the whole shared drive e.g. Limit to the minutes folder e.g. General affairs shared account → dedicated Job 4 e.g. View quotes and draft replies to send e.g. Can also export customer data e.g. Remove export; send only after approval e.g. Sales rep's personal account → dedicated Shared connections e.g. Connect only the tools you need e.g. 3 unused connections remain e.g. Remove the unused connections e.g. The admin keeps the list of connections What happens: e.g. full permissions granted during testing stay, so a wrong action reaches all the data How to check: e.g. compare the permissions column of connected apps in the admin screen with "Permissions needed" in ⑥ How to prevent: e.g. apply the cuts in ⑥ before moving to production, and have the accountable manager confirm Result: e.g. Job 2 applies. Fix by Monday What happens: e.g. it stops when the person moves or leaves, and the log does not show whether a person or the agent acted How to check: e.g. look for personal names in the "Account used" column of ⑥ How to prevent: e.g. create a dedicated account for each agent or automation and name its owner Result: e.g. Job 4 applies. Request a dedicated account What happens: e.g. it follows a request written in a received email or document all the way to sending or deleting How to check: e.g. in the tool settings, see whether sending, deleting, or paying can run automatically based on what it read How to prevent: e.g. treat outside content as read-only data and put human approval before sending, deleting, or paying Result: e.g. Job 1 has automatic sending on. Turn it off and require approval 3/4 Draw the approval... → 4/4 4/4 Log and be ready ... Vertical axis: Si... Large impact, hard to undoe.g. sending email outside the company, permanently deleting files, confirming payments Large impact, but can be undonee.g. changing shared-folder permissions, updating customer information Small impact, but hard to undoe.g. posting in internal chat, contacting fixed recipients Small impact, and can be undonee.g. summaries, drafts, labeling Rule (automatic, ... Approver What to check bef... Drafts and summaries e.g. Automatic (keep a log) e.g. Not needed e.g. Read the log in one batch once a week Posts inside the ... e.g. Automatic only for set channels e.g. Team leader e.g. Whether the channel and recipients are within the set range Sending outside e.g. Human approval e.g. The person in charge and the accountable manager e.g. Recipient, attachments, source email Deletion and payment e.g. Prohibited (a person does it) e.g. Head of accounting e.g. Do not give the agent the permission ⑫ Records to keep... Records to keep WhatAction taken e.g. the action and its target (recipient and subject of the email sent, name of the file deleted) WhyReason e.g. the reason for the request (inquiry number, the message that triggered it) WhoPeople and account e.g. who asked, who approved, and the dedicated account that acted WhenTimes e.g. time of the request, of the approval, and of the run WhereTool and data e.g. the tool used and where the data it touched is stored HowAuto or approved e.g. automatic or human approval, and which rule in ⑪ it falls under NoticeDecide the warning signs in advancee.g. an action prohibited in ⑪ appears in the log, or the number of sends is double the usual StopWho stops it, and howe.g. the person on duty pauses the run in the automation tool's admin screen RemoveRemove permissions and connectionse.g. remove the dedicated account's connection in the admin screen and disable the keys used to connect (API keys and access tokens) Check and restoreCheck the impact in the ⑫ loge.g. list the emails sent and data changed, tell those involved, and restore Regular reviewe.g. every 3 months, review the permissions in ⑥ and the rules in ⑪ Review triggerse.g. a tool update, more jobs handed over, a staff move, or a stop in ⑬ Who reviews and how to checke.g. the IT contact and each owner. Pull one week of the ⑫ log and read it → 2/4 Draw permissions ... ↙ 3/4 Draw the approval... → 4/4 Log and be ready ...
100%

Drag to move, scroll to zoom