LearnGrokA plugin that will not connect looks the same in the app whatever the cause. There are four, and knowing which one you have saves you from retrying against a policy that will never let you through.
1. It is simply not authorised yet
The ordinary path: open the plugins settings, confirm the connector is installed, reopen its detail page and choose the authentication action, then complete the authorisation in the browser, with the account you actually mean to use. Return to the app and retry the task.
The account is the part worth slowing down on. Browsers stay signed in to whatever you last used, and authorising a work connector with a personal account succeeds, then fails to see any of the data you wanted.
2. Authorisation was revoked at the other end
If access was withdrawn in the source service, reconnecting from this side does not repair it. Remove the plugin and add it back, which forces a fresh authorisation rather than reusing a dead one.
3. Your organisation blocks it
If the plugin shows as disabled by a team administrator, that is a policy, not a fault. The same message appears when you try to sign in to that server. Nothing you do on your own machine changes it.
What has to happen instead: an administrator enables it on the team plugins page and, where an allowlist is in use, adds the server's URL to it. After that, the app needs a restart before the change takes.
4. The vendor restricts it to their own administrators
Some providers only allow their own administrators to connect their endpoints. If a connector fails for regular members with a permission error from the vendor rather than from Grok Bot, that is the likely explanation, and the requirement lives in the vendor's documentation rather than xAI's.
Also worth checking
Some connectors need an organisation-provided value or configuration before they will authenticate at all. If a connector fails immediately, with no browser step, check whether it expects configuration you have not been given.
Prefer a connector: but know the alternative
Where a connector exists, the documentation recommends it over having a Bot click through the web interface; it is more reliable. But a Bot can drive browser-based tools that have no connector at all, so a blocked plugin is not necessarily a blocked workflow. It does change the security picture: a browser session on the shared computer is available to every Bot on your account, which is covered in Connecting Bots to your tools safely.
What changes
The plugin catalogue is not enumerated in the documentation and team policy controls are evolving. Check the current troubleshooting page for the present behaviour.
