Admin


 * Admin houses the company specific data for an instance. This part of the application is written in the ZEND framework.
 * The portion of the application houses the code that enables admin (the owner of the instance plus any users the owner designates as as Admin to:


 * 1) Create/Remove/Deactivate users. Users can be added singularly or a mass upload can be performed via a csv upload.
 * 2) Modify usernames and reset passwords.
 * 3) Designate other users with Admin capabilities.
 * 4) Modify and save custom theme settings including:
 * 5) Logo
 * 6) Background image
 * 7) Fonts/Color styles
 * 8) Select settings for Weekly Love emails.
 * 9) Generate Campaigns (Recognition Periods) to reward employees based upon peer recognition.


 * Architecture: The Admin application is written in the ZEND framework using Model/View/Controller (MVC) architecture.
 * Database: MySQL. Each instance is assigned it’s own database (LM_instancename) with a predefined set of tables (tewari).  Admin,Love and Review repositories share this database:
 * Tables:
 * admin_companies - stores company_id, name and theme name
 * admin_themes - saved themes, style settings
 * all_assets - image data
 * login_users - master set of users
 * love_companies - id, company name,weekly update flag
 * love_email_updates - stores settings for Weekly Update email
 * love_limits - obsolete
 * love_love - stores all love messages
 * love_schema_info - obsolete
 * love_tokens - all token requests
 * love_users - stores all user information including settings
 * love_ws_sessions - stores love sessions
 * redeem - stores data related to redemption of Recognition period earnings. Not in use.
 * review_loves - obsolete (related to old rewarder process)
 * review_periods - Recognition Period effective dates, owner, status and budget data
 * review_rewarder_distribution - loves, calculation for Recognition Period results
 * review_tokens - token requests
 * review_users - user data for review app
 * review_ws_sessions - session data