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 6 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 (128)

photo
1

I guess that WHMCS already has everything that is needed to do this, with a very small implementation.

With one single master account, the client can create sub-contacts and these sub-contacts can have different details address details and be applied to the invoices.

I think the necessary changes are:

  • Do not force sub-contacts to have an email. If there isn't an email, the user can not login, fine, but the invoices can, at least be applied to each sub-contact.
  • Each service should be assigned to a sub-contact (for invoice purposes)

I was going to say that each sub-contact needs to have its own company name but this is already there! Amazing!

So... I don't see how a simple implementation like this is still not implemented after 5 years.

Let's hope...

photo
1

how about creating a user tier:

- SuperAdmin (the one ring, to rule them all)

- Admin (can be assigned moderation of Reseller accounts and customer accounts)

- Reseller (can be assigned to manage customer accounts)

- Customer

i don't mean to circle back around on how crazy it is that this feature isn't available already... but, I am ;)

whereas, I realize that GoDaddy (and the other big players) associate account info to email address and client info... we're not GoDaddy. WE are the niche group of growing entrepreneurs, who sometimes need to bend the "norm" or write the rules. ..,to grow as small companies, entrepreneurs, and free thinkers! ;)

photo
1

This is a great way to break down the hierarchy and would work quite well if implemented.

  • SuperAdmin owns the account, and has access to everything from billing to ordering & managing services.
  • Admin has access to everything except deleting services, can create new services & assign users to them.
  • Reseller (or "Support" \ "Web Dev") have access to help customer accounts via pass resets & other tools.
  • Customers have regular access to their assigned services.

But with this ticket being open for 5+ years now, I wouldn't hold my breath that WHMCS is going to implement these much needed changes.

photo
photo
1

I've implemented this in Laravel. I have accounts and users. An account holds the billing information, the products and services as well as support tickets and such. Then you have memberships, which is user <-> account. Each user has permissions or roles on an account. This allows multiple users to belong to multiple accounts and have different roles for each. You can invite a user to join an account with specific permissions and you can remove user memberships from accounts.

An account isn't necessarily a user, and a user isn't necessarily an account: in fact, any account can have multiple users with different permissions, and any user can have multiple accounts, again with different permissions. For example, you might have a personal account and a business account, and want to keep them separate. Why make your life harder with multiple sets of credentials?

Of course, that's from the user's viewpoint. From the developer's viewpoint, this leads to authorization issues. We can't simply assume that a user has rights to everything in a given account. Some users might only need access to servers, for instance, or billing, or open tickets... because we don't know which combinations we'll see, our authorization system has to be robust.

This sort of relationship model would work great with WHMCS and shouldn't be too hard to migrate to.

photo
1

Although I'm more of a web designer than developer, I completely understand and agree that your implementation of relational Account <-> User database entries is exactly what WHMCS needs to empower independent web development consultants to work closely with clients' hosting services in a secure and convenient manner.

Surely "The World's Leading Web Hosting Automation Platform" would have the leading resources to lead the industry with a feature request that's been open for over 6 years? WHMCS, you listening? Yes? Bueller?

photo
1

I certainly agree, this really shouldn't be that difficult and I cannot imagine why this has been open for 6 years.

The concept I outlined works perfectly and should be easy enough to implement. Hopefully someone with some sense reads this and does something about it.

photo