The overarching construct that exists in Optimizely <<product-name>> is the idea of Roles. Roles are sets of permissions that are assigned to users, and manage the Admin Console and/or website functions that the user may or may not be able to access. The Admin Console includes several roles by default; however, additional roles may be created for security purposes or to implement additional or custom functionality. Security functions such as changing or resetting passwords and unlocking users are also performed within the Users section of the Admin Console with the .Net Membership Services.
Users in <<product-name>> are the central constructs that are used for the management of information and security. The Users construct contains information for accessing the website and Admin Console, such as login names, passwords and the assigned salesperson. The amount of information stored about the user is dependent on the method with which the user was created. Generally, detailed information about users that have been automatically created for new customers is stored within the customer record itself; however, fields such as whether or not the user has subscribed to emails are stored within the user record. A user record can be created via one of four processes:
Imported via an Excel Spreadsheet (Typically only done during the Implementation Phase)
Pre-populated through ERP system integration
Manually within the Admin Console
Automatically when a new customer creates an order
Customers in <<product-name>> contain customer information (such as Address, Phone Number, and so on.), and are assigned to a User. Customer records are versatile, and are able to accommodate the following models:
Single Customer to Single User (for example, A Typical B2C or direct B2B relationship). This is the default option when a customer creates an order, as illustrated in the ISC Users section.
Single User to Multiple Customers (for example, B2B implementation where a sales rep needs the ability to place orders for multiple customers).
Multiple Users assigned to a single customer (for example, A department store with multiple buyers).
<<product-name>> allows a given customer to have multiple ship-to addresses. This situation may occur when a parent company has two locations, or when a package is meant to be sent to a different person within the same location. <<product-name>> stores these addresses in the Admin Console by designating the Ship To toggle as **YES**.
<<product-name>> works off the idea that products purchased through a website by a customer will be placed into an order. An order contains information on the products that were ordered, the bill to/ship to addresses, the order number, and other applicable order-specific information.