When an integration needs re-authorizing
When an integration stops accepting the credentials Current saved for it, or a permission is waiting for someone to approve it, workspace admins see one line across the top of every page. It names the integration and its button goes straight to the fix on the Integrations page. Nobody else sees it: not the other roles, and never partner (read-only) viewers.
What the line can say
| The line says | What it means | What to do |
|---|---|---|
| (Integration) needs to be reconnected | The integration refused the saved credentials, or its access expired, so its data has stopped updating. | Choose Reconnect. For your PSA it opens that connection's Manage panel. For the others it opens the section of the Integrations page that holds the card. Enter a fresh key or sign in again, then run Test connection. |
| HubSpot lead access is waiting for approval | HubSpot is connected, but its token was issued before Current asked for lead access. Everything else keeps syncing. | Choose Re-authorize on the HubSpot card and approve lead access. HubSpot offers it on Sales Hub Professional or higher. |
| Microsoft 365 mail access is waiting for approval | Staff mailbox capture needs the application Mail.Read permission, and Microsoft reported that it isn't granted. Until it is, Current reads mail only for people who connected their own account. | In Microsoft Entra, grant Current the Mail.Read permission as an Application permission (not Delegated), then open the Microsoft 365 drawer to check. |
| Microsoft 365 needs to be reconnected | Microsoft stopped accepting your organization's approval of Current. | Approve Current for your organization again from the Microsoft 365 section of the Integrations page. |
What it watches
- ＋Your PSA (Autotask, ConnectWise, HaloPSA or Syncro), when it refuses the saved credentials. A timeout or an outage at the PSA doesn't raise the line; Sync health shows those.
- ＋HubSpot, when its access expires, and when lead access is missing on a connection that reports its permissions.
- ＋Microsoft 365: your organization's approval, and the application mail permission. A person whose own Microsoft sign-in expired gets their own Reconnect prompt instead.
- ＋ScalePad, ScalePad Quoter, Kaseya Quote Manager, ConnectWise CPQ, CrewHu and Seamless.ai, when they refuse the saved key.
- ＋Every monitoring, security, network, backup and billing connector, when the vendor refuses the saved key or the key is missing. A rate limit or a permission the key lacks shows on the card, not here.
NeverBounce, Handwrytten and Resend check a key only when you save it, so a key revoked later surfaces the next time Current uses it rather than in this line.
Several at once, and dismissing it
When more than one integration needs attention the line reads, for example, "2 integrations need attention: HubSpot, Microsoft 365". Each name links to its own fix, and Review opens the Integrations page.
The X hides the line for you in this browser. A connection that has stopped working comes back after 24 hours, because it is still stopped. A permission waiting for approval stays hidden until something about it changes, for example a reconnect that still lacks the permission. Fixing the integration clears the line on its own.