---
title: Asymmetric Team Shared HubSpot Login
type: article
created: '2026-04-05'
updated: '2026-04-05'
source_docs:
- raw/2025-12-26-sprint-planning-meeting-110895017.md
tags:
- hubspot
- access-management
- internal-process
- tooling
layer: 2
client_source: null
industry_context: null
transferable: true
---

# Asymmetric Team Shared HubSpot Login

## Overview

The team identified a recurring pain point: HubSpot's per-seat user limits prevent multiple Asymmetric team members from accessing client accounts simultaneously. The proposed solution is to create a single shared login — named **"Asymmetric Team"** — that can be added as a user across all client HubSpot portals, giving any team member access without consuming individual seat allocations.

This approach trades per-person accountability within HubSpot for broader team flexibility, and is particularly valuable when account managers need to make quick edits (e.g., copy changes in an email) without routing through whoever holds the active seat.

## Problem

- HubSpot client accounts have limited user seats (often 2–5 on starter/professional tiers)
- Individual team members are assigned those seats, leaving others locked out
- When an AM changes (e.g., Bluepoint moving from Melissa to Karly), seat reassignment is required
- Time-sensitive tasks — like updating email copy before a send — are blocked by access gaps
- Workaround of sharing credentials via LastPass exists but is informal and fragile

**Clients known to be affected as of December 2025:**
- Bluepoint
- Citrus America
- Doodla
- Scallin
- Machinery / Source / Three Gates (Asymmetric internal)

## Proposed Solution

Create a single HubSpot user with:
- **Display name:** Asymmetric Team
- **Email:** A shared team address (e.g., `team@asymmetric.pro` or similar)
- **Credentials:** Stored in LastPass for team-wide access

This user would be added to every client HubSpot portal, replacing or supplementing individual seat assignments where seat limits are the bottleneck.

## Decision & Status

Raised by Karly during the [[meetings/2025-12-26-sprint-planning|2025-12-26 Sprint Planning Meeting]]. Melissa agreed and committed to proposing it to Mark at their Monday meeting.

**Status: Proposed — pending Mark's approval.**

> "Maybe I can have Mark do that next time I'll have a meeting with him on Monday, and I can just have him switch me out, and we can do a team at. And to your point, we should do it for all of the clients."
> — Melissa Cusumano, Sprint Planning 2025-12-26

## Action Items

| Owner | Task |
|-------|------|
| Melissa | Propose "Asymmetric Team" login concept to Mark |
| Mark | Approve and implement — switch existing seats to shared login across all client portals |
| Melissa | Ensure shared credentials are stored in LastPass once created |

## Considerations

- **Audit trail:** A shared login means HubSpot activity logs won't distinguish which team member made a change. Teams relying on per-user activity history should note this tradeoff.
- **Scope:** Should apply to all client HubSpot portals, not just the ones currently causing friction.
- **New clients:** [[clients/aviary-ai/_index|Aviary AI]] is onboarding with a complex HubSpot infrastructure — the shared login should be provisioned there from the start.
- **Cloudflare/GoDaddy parallel:** A similar "who has access?" problem surfaced around DNS management for [[clients/citrus-america/_index|Citrus America]] in the same meeting, suggesting broader access-management hygiene is worth reviewing.

## Related

- [[meetings/2025-12-26-sprint-planning|Sprint Planning Meeting — 2025-12-26]]
- [[clients/aviary-ai/_index|Aviary AI]] — new HubSpot-heavy client onboarding Jan 2025
- [[clients/bluepoint/_index|Bluepoint]] — immediate seat reassignment needed (Melissa → Karly)
- [[knowledge/hubspot/hubspot-overview|HubSpot Overview]]