Reseller Account can be created for each new reseller

Login screen - 4 buttons CRUD _to look up reseller in read only mode, Update , create , delete

users table (update screen - change, reload should display updated value)

TSA internal user creates initial admin user.

... with a script to do this for QA to test

QA can add new reseller (reseller group, reseller tenant, settings - admin user can log in....)

establishes security.... does not provision any API access in this story.

******************

reseller group created and admin reseller user - TSA Admin UI (list of resellers and associated admin users) and ADD new reseller and admin user.

this is expected to be input by TSA internal user (Technical Account Manager). This is completely internal and thus no external APIs. TSA User has non-system/db access to do this.

will create login but not necessarily API credentials... still tbd- s/b case by case

Items expected to be included (part of a separate story AQ-115 - config settings) are:

Reseller company name
(primary) admin reseller user created (to manage reseller users), email, phone1, phone2
(secondary) admin reseller user

Market Location (and currency) - Location taxonomy (custom v. TSA owned)
BA Taxonomy (custom v. TSA owned
SEM repository (custom v. TSA owned)
Image repository (custom v. TSA owned v. n/a)
template repository (custom v. TSA owned v. n/a)

Time zone
Language

domain (optional)
microsite redirect (optional)

create date
modified date