Scope Difference
Compare a connector’s requested permission scopes against its explicitly approved set.
Prepare your sheet
Use one row per connector observation. Enter Approved scopes, Requested scopes. Check that every row belongs to the same review scope.
Decision rule
Use comma-separated scope keys. A dash means no scopes. Matching is exact after trimming and lowercasing.
Worked result
The fictional example contains 2 input rows. Its result is 1 unapproved scope.
| Connector | Requested beyond approval | Unused approval |
|---|---|---|
| Docs | write | None |
| Notes | None | None |
Run it on your own inputs
- Open the tool and choose Start empty or edit the example.
- Enter the inputs, resolve validation messages and review the decision sheet.
- Download the text report or print the summary for the responsible person.
Source and support
Compare a connector’s requested permission scopes against its explicitly approved set. The demonstration makes a participant’s connector authorisation explicit before shared work can use it. Benchcraft designed this tool’s inputs, decision rule and example for this office task. Reviewed source · Nate Herk | AI Automation.
Request a custom workflow. €149 one-time pilot after written scope agreement. JB Codex adapts one repeated job with a worked example and owner review.