Before an AI tool joins a workflow, its data boundary should be decided at two levels: access granted to the connected app and settings that apply generally to all conversations. The cited help documentation establishes that these controls are separate in the setup it describes. It also says connected-app access can be removed by disconnecting the app or by asking a workspace administrator to disable it.
Define what the workflow needs
A practical data boundary identifies:
- What information the workflow intends to process
- What app access is necessary for that purpose
- Which information or capability should remain outside scope
- Which general conversation settings should apply
Because app permissions and general conversation settings are separate, checking one does not verify the other. A suitable app permission is therefore not evidence that the all-conversation settings are appropriate, and the reverse is equally true.
How to check the boundary
-
Review the app permission. Identify the connected app and the access being granted or considered. The permission should match the workflow’s stated purpose rather than broader assumptions about what the tool may receive.
-
Check general conversation settings separately. Review the settings that apply generally to all conversations. These should be evaluated independently rather than treated as a substitute for the app-permission check.
-
Remove access that should not continue. The cited documentation lists two routes: disconnect the app or ask a workspace administrator to disable it.
-
Confirm the resulting configuration. Before the tool becomes part of the workflow, verify that the intended app access and general conversation settings are both in place. If access is being removed, confirm that the chosen disconnection or administrator action has been completed.
What the cited statements do not settle
The separation of controls does not establish which data a particular permission exposes in every setup. Likewise, the documented removal routes concern access; they should not be read as a guarantee about information already shared.
Before approval, the reader must still confirm:
- The actual permissions presented for the connected app
- Whether each permission is necessary for the intended workflow
- The current settings that apply generally to all conversations
- Any applicable internal access rules
- How previously shared information is retained or deleted, which requires confirmation beyond the cited statements
The safe default is to treat app permissions and general conversation settings as separate decisions, verify both, and use a documented route when connected-app access must be removed.