A connected app can still be the wrong account for your task. Before reading or changing an item, establish which account, workspace, folder, or device profile contains it.
For example, “Find the launch plan in my work Drive” identifies a different scope from “Search every Drive I have.” An agent should reuse an established account selection and ask only when the available evidence leaves a material choice unresolved.
Check the selected scope
- Open connection help.
- Inspect the app's current state and any setup selection.
- When authorization opens, verify the provider's displayed account and workspace.
- Read a small item you recognize from that scope.
- Keep its returned identity when continuing the task.
Galaxy's app list and record counts do not prove which account is currently signed in. Some providers expose account identity; others expose only an authorized session. If a provider cannot establish the account you require, report that limit rather than inventing an identity from the app's name.
From a terminal, inspect a source before discovering its operations:
indra --root "/absolute/path/to/your/Vault" manage --json '{"what":"sources","about":"google-drive"}'
indra --root "/absolute/path/to/your/Vault" actions --json '{"source":"google-drive"}'
The first checks the installed source; the second obtains its available operation catalog. Neither substitutes for checking a task's actual resource.
Understand the access you grant
| Selection or permission | What it controls |
|---|---|
| Provider account and consent | The service identity and permissions available to the connection. |
| Workspace, library, channel, or folder | Which resources a configured route can reach. |
| Local browser profile | Which authorized local browser data or session is used. |
| Operating-system permission | Whether a native helper can reach files, accessibility controls, or another local service. |
| Task instruction | Which of the available operations should be used for this request. |
Read and write access can differ. The current method schema identifies the operation's effect. For example, Connect Gmail write Actions requests the provider access needed for supported mail changes; an existing read connection does not establish those writes are available.
A broad provider grant does not mean every task should use it. Keep explicit exclusions, a read-only request, and the selected destination throughout the workflow.
Authorize again or recover saved access
For a supported connected source, Reconnect with saved access attempts to reuse its saved authorization. Authorize again starts the source's authorization flow when a fresh grant or different account selection is needed.
Google's Authorize again verifies the account used for future reads. Previously retained history remains in the Vault. If you change accounts, distinguish old retained records from current live results; a new sign-in is not an erasure operation.
Do not start another sign-in while a row says Continue current authorization. Finish or cancel that retained transaction first. Repeated clicks should not replace a challenge that is already waiting.
Disable a source
Use the exact source plugin ID returned by the installed inventory:
indra --root "/absolute/path/to/your/Vault" manage --json '{"what":"plugins","about":"gmail","limit":25}'
Then pass the observed indra-source-... ID:
indra --root "/absolute/path/to/your/Vault" manage --json '{"what":"plugin.set-enabled","id":"<returned-source-plugin-id>","enabled":false}'
Disabling stops that source's provider and retains collected data. It does not delete the external account, revoke every provider grant, erase the Vault, or remove an already published shared copy. See Permissions and source controls for choosing the appropriate control.