A plugin's enabled state, an external account's connection, and permission to a particular resource are separate checks. Review all three when deciding what Aleria should be able to do.
Review account authorization
During connection, read the provider's consent screen and use the account intended for the work. A connector can only use the access supported by its integration and the permissions of the connected account. Some providers require administrator approval for particular scopes.
If an account cannot open a file or channel in the original service, reconnecting it will not necessarily fix that restriction. Ask the service's administrator for the appropriate access.
Limit agent access
When configuring a custom agent, review its plugin access and capability choices. Give it the capabilities needed for its role. A selected plugin still needs its connector to be connected before account-backed actions can succeed.
Review automation access separately
Before enabling recurring work, check which account it uses and who can read its output. Sharing an automation's results is different from sharing credentials for its input systems.
Remove access
Disable the plugin or disconnect an account using the controls on its detail page. You can also review and revoke the provider-side authorization in the external service. Check dependent automations after either change.
See agent configuration and automation access.