Website Portal w/ Hierarchal ACL (phpGACL or similar)

I would like to add portal access to our website, so our clients can view and customize account usage information. The site uses the Alpha template from HTML5UP, with PHP for includes and dynamic language content. [login to view URL] Currently, only the header and footer are PHP includes. The primary site language is Japanese, English content will be added later. We're currently working on the English content. We can discuss the existing dynamic mechanics later, if necessary. Our customer base is made up of resellers, clients, and the client users. So a hierarchal ACL would be desired. A possible drop-in solution is phpGACL, [login to view URL] The goal of the hierarchal ACL structure is to allow resellers to add/manage clients, and clients can add/modify individual users. Also to allow clients to view/modify user account information, resellers to view/modify client and user account information. The account information should be stored in a mySQL table, the structure should contain a minimum of fname, lname, username, email, level, hash, client_name, & client_id. The final structure will be left to the discretion of the developer. Each individual account should follow standard website security practices. SQL injection prevention, password hashing, etc... Login/Logout in the menu and additional menu items, depending on session/ACL status. The account usage information is basically CDR data from Asterisk, stored in a mySQL table. Attached you will find sample data and queries. NOTE: Sample data only contains example data for a single client, using the dcontext field. You can see a mock-up at [login to view URL] There should be three (3) types of usage views available. Day, Month, and Caller specific (list of competed calls, depending on the current view). Since the dataset will NOT be live, the data will include up to the previous days records. The mock-up also shows additional client level capabilities. Simply allowing EACH client to assign names to phone numbers. I would like this functionality included in the project. The mySQL table structure should be easy enough, so I will not bother defining it. For privacy reasons, the name should be assigned at the client level. Different clients MUST define their own names. To summerize: 1. Website portal with ACL, allowing hierarchal views and management. 2. Dynamic menu, depending on login status. 3. Standard security practices. 4. Account usage information, with date based navigation options.