Update
Connected accounts belong to whoever authorized them — a teammate's login no longer deletes yours
TL;DR
A real defect with a wide blast radius: seventeen OAuth callbacks shared one writer that replaced every row for a platform with whatever the newest authorizer could see. If a colleague connected Google Ads and their access covered different accounts than yours, yours were deleted — silently.
What shipped
- Every connected account records who authorized it, keyed on the external identity from the provider rather than on the platform alone. Each grant carries its own credentials.
- Removing a connection only removes rows from the same identity. Your colleague disconnecting their Google Ads no longer takes yours with it.
- Accounts with no recorded owner are never auto-removed — rows that predate this change are preserved rather than cleaned up by a rule that couldn't know who they belonged to.
- Editors manage only what they authorized, while admins keep full visibility.
- 610 existing rows were backfilled with their owning identity so the rule applies to history, not only to new connections.
A related fix shipped alongside: the integrations page was starting an OAuth flow for every connector card as you scrolled, and only one authorization can be in flight per browser — so links appeared to expire for no reason. Connect links are now plain links that start nothing until clicked.
Who this matters to
Any team where more than one person connects accounts — agencies, in-house teams with several operators, and anyone who has ever had a connection "disappear" after a colleague signed in. On a single-operator workspace nothing changes.
Frequently asked questions
- What happened before this change?
- Each platform's accounts were replaced wholesale by whatever the most recent authorizer could see. If two teammates had access to different account sets, the second person's connection deleted the first person's rows, with no notification.
- Do I need to reconnect anything?
- No. 610 existing rows were backfilled with their owning identity, so accounts connected before this release are covered by the same rule.
- Can an editor remove an account a colleague connected?
- No — editors manage only the accounts they authorized themselves. Admins retain full visibility across the organization.