What This Update Actually Is
HubSpot is adding a new notification configuration panel inside Settings > Social > Notifications. From there, admins can pick one of four recipient options for social account expiration alerts.
- All portal admins (the current default behavior)
- The specific user who originally connected the account
- Users who have posts scheduled on the expiring account
- A custom list of specific eligible users you hand-pick
There's one important safety net built in. If the configured recipients resolve to nobody (the connecting user left, or every custom list member got deactivated), HubSpot automatically falls back to notifying all portal admins. No expiring account will ever slip through unnoticed.
This is a targeted admin-experience fix. It doesn't change how re-authentication itself works. It only changes who gets told about it.
Why HubSpot Shipped This
Here's the pattern we've seen across dozens of portals: as a company grows, admin access gets handed out for operational or compliance reasons. Legal needs reporting access. Finance needs a view into CRM activity. A senior executive gets super admin rights so they can troubleshoot access during an audit.
None of those humans manage the social accounts. None of them can reconnect an expiring LinkedIn or Instagram token. But every single one of them used to get the notification anyway.
On a portal with eight admins and six connected social accounts, that's a lot of noise. Executives start ignoring the alerts. The right person (usually someone on the social or marketing ops team) often doesn't find out until a scheduled post fails to publish.
HubSpot shipped this because notification fatigue is a real operational risk. When everything is urgent, nothing is.
How to Use It Step by Step
- Go to Settings in your HubSpot portal (the gear icon, top right).
- In the left sidebar, navigate to Marketing > Social, then select the Notifications tab.
- Review which social accounts are currently connected and note which ones have active scheduled posts.
- Select your preferred recipient option from the four available choices. For most teams, Users with scheduled posts on the expiring account is the most practical choice. It routes the alert to the humans who will feel the pain of an expired token first.
- If you choose a custom list, confirm all listed users are currently active in the portal and have the ability to reconnect the social account.
- Save your settings. The fallback to all admins is automatic and doesn't require any additional configuration.
This setting is global, not per-account. Whatever option you pick applies to all connected social accounts in the portal.
What It Touches in Your HubSpot Strategy
On the surface this looks like a minor notification tweak. But it touches something bigger: how well your social publishing workflow handles interruptions.
Social tokens expire. It's not a bug, it's how OAuth works. Every connected LinkedIn, Instagram, Facebook, or X account will eventually need to be re-authenticated. The question is whether the right person gets the heads-up in time to fix it before scheduled content fails.
Key Takeaway
Social token expiration is a predictable, recurring event. This update turns it from a fire drill (wrong people get the alert, right person doesn't know until posts fail) into a managed maintenance task. That shift reduces ops stress and protects your publishing calendar.
This update pairs naturally with the related reconnection change HubSpot shipped earlier. If you haven't read about how social account reconnection now preserves your access settings, that's the other half of this story. Reconnecting a token used to reset account-level access to 'Everyone,' which created a different kind of chaos. Together, these two updates make the social reconnection workflow significantly less painful.
From a portal hygiene standpoint, this is also a signal to audit who your admins are and why. Portals accumulate admins over time. Some of those humans need elevated access for specific functions, not for day-to-day marketing operations. If your admin list has ballooned, this update is a good prompt to run a full portal audit and tighten up role assignments.
Key Takeaway
If you're on Marketing Hub Pro or Enterprise, set this up before your next social token expiration, not after. The fallback to all admins is a safety net, not a strategy. Use the scheduled-posts option as your default unless your team has a dedicated social account owner.
Who Should Care Most
This update matters most to three groups.
- Marketing ops leaders and HubSpot admins at companies with five or more portal admins. The more admins you have, the more noise this update eliminates.
- Social media managers and content teams who own the publishing calendar. They're the ones who actually need to act on the alert, and they're the ones who've historically been left out of the notification loop.
- Agencies and RevOps consultants managing portals for multiple clients. Client portals often have executives as admins for billing or compliance reasons. Filtering them out of irrelevant notifications reduces support noise and builds trust.
If you're on Marketing Hub Starter or Free, this feature isn't available to you yet. It's limited to Marketing Hub Professional and Enterprise tiers.
George's Take
I know it's tempting to scroll past this one because it's not a shiny AI feature or a big new automation capability. But here's what I've learned after working inside hundreds of HubSpot portals: the updates that clean up operational clutter often deliver more day-to-day value than the headline features. When the wrong humans get noisy, irrelevant alerts, they train themselves to ignore all alerts. And when that habit takes hold, the important ones start getting missed too. This update is small. The habit it helps you break is not.
“Portals don't break because of missing features. They break because of accumulated friction. This update removes one piece of that friction, and that's worth five minutes of your time to configure.”
If you want to make sure your portal is set up so the right humans are responsible for the right things across every tool and workflow, that's exactly what we dig into during a Sidekick strategy session. Book a call with the team and we'll take a look at where your portal's operational friction is hiding.
Frequently Asked Questions
What are HubSpot social account expiration notifications?
When a connected social account's authentication token is about to expire, HubSpot sends a re-authentication alert so an admin can reconnect the account before scheduled posts fail. Previously, these alerts went to every portal admin. Now you can configure exactly who receives them in Settings > Social > Notifications.
Who gets social expiration notifications after this update ships?
You choose from four options: all portal admins (the old default), the user who connected the account, users with posts scheduled on the expiring account, or a custom list of specific users. If no one on your configured list is active, HubSpot falls back to notifying all admins automatically.
Which HubSpot plans include configurable social account expiration notifications?
This feature is available to customers on Marketing Hub Professional and Marketing Hub Enterprise. It's not available on Marketing Hub Starter or Free tiers. It's scheduled to release on August 12, 2026.
What happens if the configured recipients are no longer active in HubSpot?
HubSpot has a built-in fallback. If the configured recipients resolve to nobody (for example, the connecting user left the portal or all custom list members were deactivated), HubSpot automatically reverts to notifying all portal admins. No expiration alert will be silently dropped.
What's the best notification setting for most marketing teams?
For most teams, selecting 'Users with scheduled posts on the expiring account' is the most practical choice. It routes the alert directly to the humans who will be affected by a failed publish. If you have a dedicated social media manager, adding them to a custom list is also a solid option.
Does this setting apply per social account or to all accounts at once?
The notification setting is global, meaning it applies to all connected social accounts in your portal. You can't set a different recipient rule for LinkedIn versus Instagram, for example. Whatever option you configure in Settings > Social > Notifications covers every connected account.
