Start with permissions people can understand

Explain access at the point of need

A workflow that compares records may initially need read access. A later recovery action may require a separate permission to create or update something. Those are different decisions.

The interface should connect the permission to a concrete task, such as reading paid orders or retrying a supported transfer. A vague request for full access makes the decision harder to assess.

Separate connection from approval

Connecting a tool establishes a permission boundary. It does not mean that every possible action within that boundary should happen automatically.

Individual approval and bounded standing approval are proposed options. Both should show the allowed action, the conditions under which it applies and the cases that return to a person.

• Show which account and system are connected.
• Describe what the workflow can read and change.
• Keep an approved action within its operating rule.
• Provide an understandable way to pause or revoke access.

Design for missing access

A workflow may reach a point it cannot inspect. The finding should identify the missing permission and explain how that limits the result.

The person should be able to request the necessary access or continue with a manual review. The interface should preserve the evidence already gathered instead of forcing the work to start again.