When an integration needs re-authorizing
What admins see when an integration loses access, stops syncing, has unlinked accounts or lacks a permission, the email when a PSA refuses, and the fix.
On this page · 4 sections
When an integration stops accepting the credentials Current saved for it, has not synced for more than a day, 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, usually on the Integrations page. When your PSA is refusing what Current reads, it opens Sync health, where each refused area is named. Nobody else sees it: not the other roles, and never partner (read-only) viewers.
You don't need to open Sync health to check on your integrations. Current watches them, and this line is how it tells you one needs you. The line is red when a connection has stopped, and purple when a permission is only waiting for approval or some accounts still need a company.
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 that tool's drawer on Settings › Integrations. Enter a fresh key or sign in again, then run Test connection. |
| (Integration) hasn't synced in over a day | Current has not been able to sync with the integration for more than 24 hours, whatever the reason. These are the same integrations the daily "Sync needs your attention" email lists. | Choose Review to open the integration and read what went wrong. For your PSA, the connection's Manage panel shows which parts are behind. The line clears on its own once a sync succeeds. |
| (Integration) has 3 accounts that aren't linked to a client yet | The integration is working, but some of its accounts (organizations, sites or tenants, depending on the product) aren't linked to one of your companies, so what it reports about them shows nowhere. Accounts you chose to ignore don't count. The line uses your workspace's word for the people you serve. | Choose Map them. It opens the integration's panel on its company-mapping list: link each account to its company, or Ignore one you never need. The line counts down as you go. |
| (Your PSA) is refusing part of what Current reads | Your PSA accepts Current's sign-in, but the account Current connects with is missing read permissions on two or more areas, so those areas stop updating. Everything else keeps syncing. | Choose Review. Sync health names each area that is refused. Grant the missing permissions to that account in your PSA, and those areas sync again on their own. The email Current sends about it names the exact lines to grant. |
| 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 press Manage on the Microsoft 365 card at the top of Settings › Integrations to check. |
| Microsoft 365 needs to be reconnected | Microsoft stopped accepting your organization's approval of Current. | Choose Microsoft setup on the Microsoft 365 card at the top of Settings › Integrations, then Organization approval. Sign in at Microsoft as a global admin. |
What it watches
- Your PSA (Autotask, ConnectWise, HaloPSA, Syncro, Rev.io or SuperOps), when it refuses the saved credentials, or when the account Current connects with lacks read permissions on two or more areas. A short timeout or outage doesn't raise the line; one that lasts more than a day does.
- Every integration, when it has not synced successfully for more than a day, for any reason. A workspace that is read-only for billing doesn't get this line, because its syncs are paused on purpose.
- 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, SimpleSAT, GlassHive and Seamless.ai, when they refuse the saved key.
- Slack, when the Current app was removed from your Slack workspace or its access was revoked. Choose Connect Slack again on the Slack card.
- 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.
ZeroBounce, 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. Accounts waiting for a company stay hidden until more of them appear; mapping some of them never brings the line back. Fixing the integration clears the line on its own.
The email when your PSA refuses Current
When your PSA refuses Current for a reason only your workspace can fix, Current also emails the people your workspace sends integration problems to. Two cases qualify: the account Current connects with is missing a read permission (a ConnectWise API Member whose security role can't read companies or time entries, for example), or the PSA refused the saved keys or secret. A timeout, an outage on the PSA's side or an error on Current's side never sends one.
- The first email goes out about 30 minutes after Current first sees the refusal. It names every area that stopped syncing, the exact permission lines to grant (for ConnectWise, each security role line to set to Inquire Level: All) or the keys to replace, where to make the change in your PSA, and a button that opens your PSA's panel on the Integrations page.
- Surveys are listed on their own, as optional: Current reads your PSA's own surveys only if you use them for customer satisfaction scores, and you can switch Satisfaction surveys off in the PSA panel instead. A refused survey permission alone never keeps these emails coming.
- While any required area is still refused, a reminder follows 3 days after the first email and a last one 7 days after it, each naming only the lines still missing. After that the daily "Sync needs your attention" email picks the problem up again, and anything newly refused starts its own first email.
- Once nothing required is refused any more, one short email says your PSA is syncing again. If the problem comes back within a day, it counts as the same one: no new first email, and no second note. Current never sends more than two of these emails about one problem in a day.
- Until a day after the last reminder, the daily "Sync needs your attention" email leaves out what these emails already named, so you don't get both about the same thing. Disconnecting the PSA closes the problem without a note; reconnecting it while it is still refused starts over with a first email.
They go to whoever your workspace sends integration problems to: every tenant admin, unless a tenant admin changed "An integration starts failing" under Admin → Notifications (switching it off there stops them for everyone). Partner (read-only) viewers never get them, and neither does a demo workspace or one whose Current subscription is suspended or has ended. To stop them for yourself, open Notifications from your account menu and switch off Sync attention, the same switch as the daily email.