You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: devlog/_plan/260624_codex-multi-auth-security-implementation/40_phase40-manual-import-disable.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -219,7 +219,7 @@ Required imports:
219
219
Assertions:
220
220
221
221
-`checkAccountIdCollision("shared-team-account", "member-b@example.test")` returns no collision when an existing pool account has the same ChatGPT account id but a different email;
222
-
- Correction 2026-06-27: `checkAccountIdCollision("shared-team-account", "MEMBER-A@example.test")`also returns no collision. ChatGPT account id plus email is not an authoritative duplicate key because one user can legitimately hold both personal and business subscriptions. Duplicate prevention remains scoped to local alias checks and exact OAuth refresh-grant fingerprint matches.
222
+
- Correction 2026-06-27: `checkAccountIdCollision("shared-team-account", "MEMBER-A@example.test", "business")` returns no collision when the existing account is personal. Personal and workspace subscriptions are separate duplicate buckets because one user can legitimately hold both. Within the same bucket, the existing ChatGPT account id plus normalized email collision guard still applies.
0 commit comments