Make.com Access Consolidation — 2026-01-16

Overview

During the ^[1], the team discovered that Make.com access was fragmented: Mark had signed up for a separate account using his Google login, while the team was operating in a different environment. This left Mark's account isolated and the consultants without access to the shared workspace.

The resolution was to consolidate everyone onto the company's existing paid account and cancel the duplicate.

What Happened

Mark had independently signed up for Make.com using his Google login, creating a separate organization ("Asymmetric Marketing") with only himself as a user.
The team's working environment was a different account, stored in LastPass under an internal login.
Mark's invitation in the team environment showed as expired/invalid, meaning he was effectively absent from the shared workspace.
Consultants also lacked access to the Make.com environment needed to build and manage automations.

Resolution

Mark identified the company's paid account via LastPass.
Mark invited Melissa, Isalia, and the external consultants to the paid account as admins.
The duplicate account Mark had created independently was flagged for cancellation.

Action Items Generated

[ ] Cancel duplicate Make.com account (@Melissa Cusumano)

Lessons & Best Practices

Single source of truth for tool access: All team members and contractors should be onboarded to the company's canonical paid account, not personal or ad-hoc signups. Credentials should live in a shared password manager (LastPass) from the start.
Invitation hygiene: Expired invitations should be re-sent promptly. If a user reports an invalid link, generate a fresh invite rather than troubleshooting the old one.
Admin vs. member roles: Consultants were granted admin access in this case. Consider whether that level of access is appropriate on an ongoing basis or if it should be scoped down once automations are stable.

^[2]
^[3]
^[4]