Features per user

sparek-3

• August 02, 2018 11:39

This has always annoyed me. Why are features enabled per package and not per user? This just seems stupid to me. If I want most users to not have the new Terminal interface, but if I want one or two users to have access to it, I have to create a new feature set, then create a package with the same values that they currently have but with this newly created feature set, and then upgrade/downgrade the user to that new package. Why? Why can't I just give that user access to the Terminal feature?

• 

  cPanelMichael

  • August 02, 2018 18:00

  Hello @sparek-3, Associating feature lists to packages instead of individual accounts is helpful for web hosting companies that want to offer the same set of features to all accounts associated with a specific package. This is especially useful for web hosting companies that host a large number of accounts where it's not practical to manage separate feature lists for each user. That said, I do understand that every situation is different and there is benefit to an alternative way of assigning feature lists to accounts. I encourage anyone else seeking similar functionality to vote and add feedback to the existing feature request (opened by @sparek-3) at: Enable Feature via username instead of via package Thank you.

  0
• 

  sparek-3

  • August 02, 2018 18:21

  And if anybody comes across this thread and that feature request, realize that that feature request entry is over 3 years old. So... don't hold your breath.

  0

Please sign in to leave a comment.