Bug: EXT_PERM_USER from connector prevents creating the corresponding real user
Describe the Bug
When a connector with external permission synchronization (e.g. Google Drive) encounters an external user email, Onyx creates an EXT_PERM_USER placeholder for that email.
Later, an administrator attempts to create a normal Onyx user using the same email address.
Onyx reports that the user already exists, but the email address is not shown in the normal Users list.
This prevents the administrator from creating the real web-login account.
Expected behavior
External permission-sync identities (EXT_PERM_USER) should be distinct from actual Onyx web-login users for user-management purposes.
If an administrator creates a user whose email corresponds to an existing EXT_PERM_USER placeholder, Onyx should either:
- automatically promote the EXT_PERM_USER to the appropriate web-login account, or
- explicitly offer/perform the placeholder-to-user conversion.
The external permission identity must remain usable for document ACL synchronization.
Actual behavior
The existing EXT_PERM_USER email causes "user already exists", while the placeholder is not visible as a normal user in the Users UI.
Environment
Onyx version: [Latest] Deployment: Self-hosted Docker Connector: Google Drive [connector type] External permission sync: Enabled
Source: onyx-dot-app/onyx