User Manager/Customers

• Customers are service providers. They use web interface to manage users, credits, routers;
• Customers are hierarchically ordered in a tree structure - each can have zero or more sub-customers and exactly one parent-customer;
• Each customer can have same or weaker permission level than it's parent;
• Each customer has exactly one owner-subscriber.
• Customer with owner permissions is called subscriber. Subscriber's parent is himself;
• Customer data contains:
  • Login and password. Used for web interface;
  • Parent. Enumerator over customers. Used to keep the hierarchy of customers;
  • Permissions. Specifies permission level;
  • Public ID. It's an ID used to identify customer. When a user wants to log on the user page or to sign up he/she needs to specify, which customer to use (because user login names are allowed to be equal among several subscribers). To keep customer login names in secret (for security reasons) this field is used to identify customers ( subscribers);
  • Public host. Only for subscribers. IP address or DNS name specifying public address of this User Manager router. Payment gateways use this address to send transaction status response. This field has sense only if users access User Manager site through local IP address (for, expample, http://192.168.0.250/user) and another address is used for public access (for example, http://userman.mt.lv/user).
  • Company, city, country. Informational;
  • Email address. Used to send emails (for ex., sign up information) to users;
  • User prefix. Used to separate users between customers of one subscriber;
  • Sign-up credit. Used to specify prepaid time a user gets automatically on successful sign up. Note: sign-up credit will always have zero price, no matter what the real price is;
  • Sign-up email subject. When a user signs up, he/she receives an email with account activation information, called sign-up email. Subject of this email is configurable.
  • Sign-up email body. Text template of sign-up email. Must contain several specific string constants:
    •  %link% - will be replaced with link to account activation page;
    •  %login% - will be replaced with login name of newly created account;
    •  %password% - will be replaced with password of newly created account.
  • Authorize.Net fields:
    • Allow payments. When checked, users are allowed to us this payment method;
    • Login ID, Transaction Key, MD5 Value. Authorize.Net merchant attributes. Must match those specified in Authorize.Net Merchant gateway security settings;
  • Date format. Used on web pages for data representation. Only allowed formats (listed in drop-down) can be used. When the value doesn't match any of allowed (it's possible to enter any value from console) formats, default is used. See date character constants:
  • Currency. Used for payments and money-related data representation on the web page;
  • Time zone.