EE and CI, to use it or not to use it

[eluser]RJ[/eluser]
Hello,

Hoping to get some input here because I'm not at all familiar with Expression Engine(EE).

I'm currently building a program using code igniter, I will need to create a back end administration with ACL restrictions - like:

Corporate
Customer
User
User
Customer
User

Where each "Customer" will have a white label version of the program I'm writing to administer; viewing their own database / customer information.

I haven't put a ton of thought into this yet, but I need to start somewhere, I guess the question is, what would you suggest when attempting this type of ACL restrictions?

Can I use EE to specify what DB a customer has access to view? And have sub account(users) under the main customer? Should I use EE or write something myself?

Any input is very much appreciated!

1 more question - is there a good db admin plug-in for CI? I know Symphony has an admin generator: http://www.symfony-project.org/screencas...-generator

[eluser]Aken[/eluser]
Unless you have a need for a lot of the other EE features, I wouldn't use it just for its ACL features. There are lots of options available in the Ignited Code section of these forums, take a look and keep an eye out for anything that says "Authorizations" or something similar.

As for a DB admin, CI has Scaffolding, that's about it. You can read about it in the User Guide.

[eluser]RJ[/eluser]
Thanks Aken. Have Scaffolding, noticed it's been depreciated and will likely be removed in future releases (?).