When the client changes their email from "Your profile" in WHMCS 8.1, no 'verification' is done on their new Email.
In WHMCS 7.X, when the user changes email, the new email is considered as 'unverified' and it needs to be verified.
Upon contacting the WHMCS support team, they said:
===
For e-mail verification, it takes into account the e-mail address on the Client themselves - it doesn't consider the login User. Therefore if you change the e-mail address on the User itself, it won't affect the e-mail verification status show on the client area (usually the "Your Profile" page).
===
I request WHMCS to verify email when changed in "Your profile" page like it was in WHMCS 7.x because this is important too.
WHMCS Team Clarification:
This request is about maintaining synchronization between the Account email address and User email address, if there is a 1:1 relationship (ie. the Account is associated with just one User who is the Owner, not associated with any other Accounts). Updating the User or Account email address would also update the value at the other location, either via a prompt to the user or automatically.
This would then trigger the verification of the Owner User's new email address, and in turn potentially simply account management for those who don't need multiple Users.
Merged Ideas
Update Users when changing Client Account details
As a User who is the Owner of a single Client Account, I would like to present the option when changing the Client's Account's details to also apply those changes to the User details.For example changing the email address on the account could present an option "would you also like to update the user address" or pop a warning "this isn't going to behave the way you expect, you need to update your email address in 2 places despite you being the only user who is also the owner".For Client Account with a single User who is the owner, it would save time and potentially confusion for accounts belonging to one individual.
Upon change of email address in an account, either change it or suggest changing in the Owner User as well.
Accounts and Users have different email addresses. This can be a good thing and I'm glad it was done this way for optimal handling of one user with access to multiple accounts.However, one process flow that wasn't considered when these were separated is the change of an email address. Frequently a User logs into an account to change the email address, they find the profile fields for the Account and change it. Then they're super confused as to why they still login with the old email address - this is because they didn't change the *User* email field as well.One of two things should happen to fix this process flow failure:1. When changing the email address in the account profile area, if the owner email address is the same, then the owner email should change automatically as well (with a message indicating it will be changed too), or2. After changing the email address in the account profile area, if the owner email address is now different, a warning should appear indicating that the Account email was changed, but the Owner User wasn't - would you like to update the owner User email address as well? Yes/No where clicking Yes updates it.Personally I think (1) would make a lot of sense, but can understand how you might prefer (2).
8 Comments
Login to post a comment.
* https://developers.whmcs.com/hooks-reference/client/#clientedit
* https://developers.whmcs.com/hooks-reference/user/#useredit
The introduction of Users, separates the Billable entity from the individual who is logging in to perform actions on the account. As a result the email address of the human actor (User) may change, but it would not always be correct to assume that the billable entity (Client Account) contact details should also change.
In WHMCS v7, changing the sub-account's email address would not change the Client's Accounts email address.
If you'd like to update the Client Account's email address whenever the User is updated, I'd suggest creating an Action Hook, which can use the API to make the edit to the Client Account record: https://developers.whmcs.com/api-reference/updateclient/
Then trigger it whenever a User is edited: https://developers.whmcs.com/hooks-reference/user/#useredit
For more information on the API and Action Hooks, please refer to https://developers.whmcs.com/hooks
I second his request, the reason for it is that we're not talking about updating the "sub-account" when changing "client account", we're considering that the MASTER account that is originally associated with the account you register with WHMCS it generates a Client account and User account with the same email this is the MASTER KEY, I agree that let say I am changing the Client account for the master, it would popup with something like "Would you like this email associated with the Master user as well" and a simple "Yes / No" option, this way we don't have to update both USERS master and CLIENT original from A to B when a client needs it to be changed.
The hook idea is also nice but why not just implement it, fairly easily, anyway this got my vote.
The email verification is done on the Client Account email, this is the entity which owns the services and to whom the invoices are issued. Therefore this is the email address which is verified.
Please do share the benefit you would gain from verifying the email address used just for login purposes?
The benefit will be:
1) Security for hosting company (one's the email verified, it can be changed and then user can purchase anything using the "new email" because billing will be generated with the 'new email') [request you check it how it works because upon my testing, the invoice was sent to the new email owner]
2) While registering domain name, it is compuslorly as per ICANN rule to verify Email address to ensure ownership of domain and 'techincally' the 'new email' will be the owner of the domain. [Again I request you to check it once as you said invoice and services will be issues to 'Client Account email' which is not happening and Domain registrar module is using the new email]
If I tested more, I am sure I can give more valid reasons for the email verification but the 2 mentioned above are the main reason for this feature to get implemented in the next update.