We’re a hosting and I.T. services provider with our own front-end control panel that’s built a-top CodeIgniter 2.x framework (http://totalserve.net.au/control-panel/).
Our front-end codebase is around 120k lines of code, so not too large or too small. Back end administration and the actual administration of server/services is all completely separated from the control panel. Basically, our control panel is just for user interaction and talking to our back end APIs.
Anywho, we’re now in the meaty stages of completely revamping our website and one of the things we’re looking to do is plug both our site and control panel into a CMS. Basically, what I am after is if a customer is logged into our “site”, he/she is also logged into the control panel/forums/etc so we can share functionality and benefit from code reuse.
Given EE is built a-top CodeIgniter, my questions are:
Just how flexible is the user/group management, can we extend it’s functionality?
Our current authentication system has the concept of groups of groups. For example, we’ll have group:CompanyABC and in that group is “Admins”, “Staff” and while “Admins” have full permissions - they only have full permissions within their group, so they only see/can modify other users within the parent CompanyABC group.
Does EE have this concept out of the box? If not, is the framework similar to CodeIgniter in that we can extend these basic libraries?
If we can extend this functionality, can we extend these code components via Add-ons? In an ideal world, I’ll love for us to write our “Control Panel” as an add-on without having to touch the EE code at all!
I’m not too worried about technical support (we have developers in house, that should be able to figure things out). But can anyone tell me what the policy is on security updates/etc?
Thanks for reading.