- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2023 07:33 PM
We have 3 workspaces - 1 old version in one AWS account, 2 latest versions in another.
We are PAYG full edition, not using SSO.
Our admins (existing DBX users in the `admins` group) can invite new users via the Admin Console from the 1 old and 1 new workspace.
But from the 2nd new workspace we get the error "Failed to add user: A user with email ... or username ... in different cases already exist in the account"
The user definitely does not exist in that workspace's Users.
I did wonder if it was because he's been added to the other workspace in the same AWS account (the users experiencing this error do exist in the other workspace).
But the user lists are different.
And the users cannot access the workspace.
So I assume this is unlikely to be the issue?
(on a side-note it would be nice to see the grammar corrected and a better description of the error cause)
- Labels:
-
AWS
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2023 12:17 AM
So it would appear that, because the user already existed in a different workspace in the same AWS account, that the 2nd workspace invite email needs to match the user INCLUDING THE CASE (i.e. its case-sensitive)!
😞
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2023 11:48 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-27-2023 12:17 AM
So it would appear that, because the user already existed in a different workspace in the same AWS account, that the 2nd workspace invite email needs to match the user INCLUDING THE CASE (i.e. its case-sensitive)!
😞
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-21-2023 06:48 AM - edited 11-21-2023 06:51 AM
We are facing same issue, We are on azure. @AndyAtINX you mean if user exist in workspace with abc@gmail.com we should add the user in workspace2 with abc@gmail.com not ABC@GMAIL.COM.
if this the case we tried this and its not working for us.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-21-2023 05:16 PM
@Schneider-Electthat is what worked for us - repeatedly. Case needs to match exactly
Maybe a different issue with same effect?
Other thoughts are maybe leading/trailing spaces or different char-sets?

