Updated for clarity on phone number

main/docs/authenticate/database-connections/flexible-identifiers-and-attributes.mdx

@@ -34,7 +34,7 @@ The following is a list of potential issues you may encounter while configuring
 
 * If the scope `phone` is not specified in the authorization request by your application, you will not receive the `phone_number` claim. To learn more about scopes, [read Scopes](/docs/get-started/apis/scopes).
 * Your Get User custom database action script must be valid when **Import Users to Auth0** is set to **on.** To learn more, [read Configure Automatic Migration from Your Database](/docs/manage-users/user-migration/configure-automatic-migration-from-your-database).
-* Each user must be assigned a unique username, email address and phone number if **Custom Database with Import Mode** is set to **on**.
+* Each user must be assigned a unique username, email address, and phone number regardless of connection type. The phone number is unique even if not added as an attribute.
 * If you use the custom database action script Change Password and want to set `email` and `email_verified` to `True`, you must return the preferred `email_verified` state on the object. To learn more, [read Change Password](/docs/authenticate/database-connections/custom-db/templates/change-password).
 * If you use a custom database connection with Import Users to Auth0 toggled off, you must align your user profile properties with the Auth0 normalized user profile. To learn more, [read Normalized User Profile](/docs/manage-users/user-accounts/user-profiles/normalized-user-profiles).
 * If you use a custom database connection with Import Users to Auth0 toggled on, Auth0 will check for uniqueness of `phone_number` and `phone_verified.`