Your permissions worksheet
Use this beside the permissions walkthrough (opens in a new tab). A permission lets an app reach information or perform a kind of action. An approval is your decision about a particular action. A written request does not change the connection’s actual access.
1. Name the help before choosing access
Start with a job: “Prepare replies to selected routine supplier messages.” A draft from pasted text needs no inbox connection. Finding new messages needs supported, approved reading access. Sending a reviewed reply needs supported sending access as well as the required authorization.
2. Inspect before confirming
Open the service in your AI tool’s actual app/plugin connection settings. Check the account identity and read the consent screen. Write what the permission really covers, not what you hope the prompt restricts. Cancel before granting access if you are only learning or the scope is too broad.
| Choice | What it could enable | What remains unavailable without it |
|---|---|---|
| Selected permitted message text | Explain or draft from that text | Independent inbox inspection |
| Approved email reading | Find and summarize permitted messages | Sending, unless separately supported and granted |
| Approved email sending | Send an authorized reviewed message | Calendar changes unless separately supported and granted |
| Approved calendar reading | Inspect appointments and possible conflicts | Creating or changing events |
| Approved calendar editing | Make a specifically authorized supported change | Other accounts or unsupported actions |
These are capabilities to inspect, not a promise that every product separates permissions this way. A search filter such as “vendor mail only” may not narrow the underlying access.
3. Make the decision and test only what was approved
Job and useful result:
Tool, source service and exact account:
Information the actual permission would expose:
Actions the actual permission would enable:
Why that access is needed, or why selected excerpts are enough:
What it cannot do if I decline:
School approval and suitable data boundaries confirmed by:
Actions that still require my specific decision:
Harmless teaching task to try:
Where I will inspect the actual result in the source app:
How I remove access in the tool and source service:
Filled example: Supplier-reply drafting, no connection. Supply one fictional request for Thursday at 2 PM, ask for another-option draft, and inspect that it does not claim calendar availability. Copy a checked reply into the normal message app yourself. No automatic delivery or calendar access is enabled.
If you later use an approved teaching account, test one permitted read and a harmless action that must wait for approval. Inspect the source app afterward. To stop access, use the connection-removal controls and review the source service’s authorization list; deleting a conversation alone does not revoke a connection. If an expected permission is absent, keep the task manual rather than assuming different wording will grant it.