Has anyone else come across the issue where the user role is now required? My org doesn't really use them except in specific circumstances for our Development officers (my previous org didn't use them at all so I know I'm not alone in this). I noticed in August when I was reactivating a user with a standard license and was forced to pick something. It did the same thing when I created a new user (also with a standard license) as well. It defaults to the first choice on the list if you have any roles created, and I can't select none.
I asked SF Support when I couldn't find any documentation on it. They thought it might have been a setting I turned on, but were surprised when they opened their own demo org and saw that it was required for them too. They told me this morning that they were asking some higher ups about it.
I've attached screenshots of my account where you can see that when my account was created, a role was not selected but if I were to edit it, it defaults to the first choice on the list and is required.
@* Salesforce Administrators * @Nonprofit Success Pack @Admin Addicts
I've run into a similar issue. We also do not utilize roles. I had a non-sys admin who was responsible for creating new user records, and he had permissions via the manage internal users permission. I forget when it started, one day he could no longer save new records. He could still edit existing ones. I am pretty sure it is also related to roles. He did not have the 'not specified' option that I see as an admin. Nothing we tried restored his ability to create new user records, but we did not bother calling Salesforce for it, maybe we should have? I created a screen flow that he now uses to create new user records.