Feature Requests
Share ideas, discuss and vote on requests from other users in community
 

Multiple Billing Accounts using One Login

Rob Dokuchie shared this idea 5 years ago
Under Consideration

We desperately need to be able to use ONE login for multiple billing accounts.

I'd prefer a username and password login, after which the client could view each of their billing accounts.

We have multiple clients who have multiple businesses, but only want to use one email for correspondence. Changing WHMCS to utilize username/password instead of email/password would allow us to create seperate billing accounts under the same contact.

No sub accounts won't suffice, no forwarders are not a solution, and yes we do have more than one client who needs this.

Comments (115)

photo
1

I 100% agree this is needed. With the email address needing to be unique, but when someone needs to have multiple accounts, and/or multiple sub-accounts (companies wanting separate billing for different purposes, developers that refer customers to you and need to have a sub-account on each one), this is a constant issue in troubleshooting ways to work with this system as is.

To make this work in the ideal manner, it should be as follows:

- Create an order

- Create a unique profile to attach that to. Sort of like being the "main" account

- Advise of other profiles you want associated with this product.

- Select what level of access they will get (billing, full access, etc)

- Enter their email address to get an invite to sign up

- Invite goes to that persons email address.

- They continue to sign in.

WHMCS would need to be more like a CRM system, with each profile and the associated products they have access to. If it just replaced email addresses with usernames, it would at least be a start but still not really addressing the big picture, which one username would log you in to all services you are able to see, and do something with.

photo
1

Nice that this is under consideration. Need some action on this.

Email is a horrible way to setup a user. One simple reason is a email may become unavailable for various reasons.

You must have the email/ username set to unique. Makes sense since your searching on it and obv expecting a single return. But you must have a primary key set to that record and thats already unique.

The dilemma is how to convert what people have setup now to something that can be changed. Since you also have a password that joins on the username why not create a username field that YOU control. Creating a unique field for this is cake. Then tell people who try and use their email as their username that an email has been sent with their new username... your created field, and to use that. A simple check to see what was entered into the username will tell you if they used an old email or the new username. Now you have a way to assign the username, find their account based on that, much better then email and faster then a text search and a way to allow multiple accounts with the same email. If you are running a normalized database then your set.

Its not going to be easy, but not insurmountable. What is currently in place is not workable unless you are billing one entity.

photo
1

I was wondering if there was any progress on this?

It would be extremely useful for reseller accounts!