Asymmetric HubSpot Access & Seat Management

Overview

During the March 2026 Asymmetric marketing strategy kickoff, the team identified and resolved a recurring HubSpot access bottleneck. Multiple team members had been sharing a single login (Melissa's) due to unclear seat assignments. The issue was resolved in-meeting by reassigning an unused seat to Melissa and clarifying each person's access level.

Context

The Asymmetric HubSpot account had accumulated stale seat assignments over time. Chris Ostergaard held a core seat he no longer needed. Meanwhile, the active team — Karly, Avoke, Isalia, and Melissa — had largely defaulted to logging in under Melissa's credentials, creating friction whenever two-factor authentication codes were required.

Raphael (a developer/contractor) had his own super admin seat but had apparently forgotten his credentials and was requesting access through others, suggesting the team had lost visibility into who held what permissions.

Resolution

Mark reviewed the seat assignments live during the call and made the following changes:

• Chris Ostergaard's core seat was removed (no longer active with the team)
• Melissa Cusumano was invited and assigned the freed core seat
• Raphael was confirmed to have his own super admin + core seat — no action needed
• Mark retains admin access
• Karly has her own seat linked to the Asymmetric HubSpot instance

Current Seat Summary

Operational Notes

• The team had normalized sharing Melissa's login as a workaround, which caused periodic disruption when MFA codes were needed
• HubSpot's "remember me" session appears to last approximately two weeks before re-authentication is required
• Client HubSpot accounts (e.g., Doodla) are separate instances; seat management there depends on client subscription tier and is handled case-by-case

Related

• ^[1]
• ^[2]
• ^[3]