
kanakos.23654 (Customer) asked a question.
Question Regarding Updating the Default Okta User Profile Policy
Dear Okta Team,
We have added a user profile policy under Okta Admin Console > Security > User Profile Policies to allow users to sign in using their email addresses, in addition to their existing username format of LastName.FirstName.
Going forward, we would like users to be able to sign in with their email addresses to Okta and all applications integrated with Okta.
Would it be safe to update the default policy as well to allow sign-in using email addresses? If changing the default policy could cause any issues or have any potential impact, we would appreciate your advice.
Thank you in advance for your guidance.

Hi @kanakos.23654 (Customer) , Thank you for reaching out to the Okta Community!
Yes, you can update the default User Profile Policy to allow sign-in with an email address, but you should review a few potential risks and configuration impacts before making the change.
Because the default User Profile Policy acts as a "catch-all" and applies to the Okta Dashboard, administrative access, and any applications that do not have a specific policy assigned, updating it has org-wide implications.
Keep and eye out for the following:
1. Uniqueness Conflicts (Shared Email Addresses)
When you allow an attribute (like email) to be used as a sign-in identifier, Okta relies on that value being strictly unique across the entire directory.
2. Attribute Permissions (Read-Write Exposure)
Depending on how you configure the enrollment form within the User Profile Policy, custom identifiers sometimes require the attribute's permission to be set to Read-Write in the Okta Profile Editor.
3. Increased Attack Surface
Using a proprietary LastName.FirstName format provides a mild layer of obscurity, as attackers must guess or know your internal naming convention.
4. Downstream App Assertions Remain Unchanged
Changing the User Profile Policy only changes how the user authenticates into the Okta Sign-In Widget. It does not alter the underlying username format sent to downstream applications via SAML or OIDC.
Recommendation
Before updating the default policy:
If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope my answer helps!
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Collect them all. Learn a new skill and earn a new Okta Learning badge.
Just released: More Okta Community badges just added