[Reposting this in this community block]
Hey y'all! I'm trying to create a user profile for a staff, but I keep getting an error message that the username is duplicated. I did check the list of all active and deactivated profiles and there is no other username on my organization list that comes close to the one I'm trying to create.
The kicker out of this is that my organization uses the single sign on feature that is tied to our google workspace, so that means that I need the username to match the email address of the staff. My organization owns the email domain, and according to our IT this shouldn't happen - at least in regards to the username.
At the moment I have the staff use the authenticator app with a different username. But I really want to move away from the app and use the single sign on.
Please send some help!!!!!
---
***For context, I did read the Salesforce article "Error 'Duplicate Username' when you create a username"****
https://help.salesforce.com/s/articleView?id=000385306&type=1
Update: it turns out that our SSO users were having problems after all. I confirmed that one of them had logged in recently before posting above, but it turns out that he still had access to a direct login at that time.
We are now told by our IT consultant that the workaround on the SSO side is pretty cumbersome. The solution on the Salesforce side is a bit cumbersome, too, but they think is the way to go - and at least it IS a solution, not a workaround. This is the process that I am currently going through with Salesforce support.
1. They have confirmed that a couple of our users have existing logins in a Salesforce org that is not under our control.
2. But they can't tell us which one because it is a violation of confidentiality with the company or organization that controls that database.
3. They suggested that we have the users search their email for the confirmation message from Salesforce sent when the account was created.
* One of our users discovered a better route by looking in his password manager - he found two Salesforce logins identified with the Salesforce logo.
4. With the relevant orgs now identified, we will be working directly with them to implement alternate usernames in THEIR org, so that we can use the SSO-friendly usernames in ours.
I could have figured out where the real problem was sooner - in retrospect I already knew both of these funders were using Salesforce - but my brain was stuck in thinking no one else should be using our email addresses. However, in both of these cases, it was a fully appropriate use of both their systems and ours - the accounts were created when we were under contract to them for purposes of administering the contract. We and these two funders are all in the non-profit space, but I think that any kind of contractor would be particularly likely to encounter this problem.
