Page 35 - EconiqTA

35

Conversation Experience Requirements

User Accounts & Access

• A Windows login username with administrative rights on the Hub server and initially administrative
rights on the client desktops. Administrative rights on the client desktops can be removed once the Hub
client applications are installed and the Hub is working correctly.

• Valid Client Application logins for all possible “frontline user types” of the Clients Application. Typically
we configure the Hub application using the Client’s Test System and therefore require logins for the test
system.

• A secondary Windows login account with the equivalent access rights as frontline users. This account
will be used to test the Conversation Hub under normal running conditions.

• If the referral and on boarding system is to be used then we will require an email account to send and
receive test referral and on boarding emails. Confidential and Proprietary - Copyright © 2017 Econiq

• Conversation Engineers will need to transfer code to the server at regular intervals. Typically we do this
through read access to a USB port and device. It can also be done by email or online file transfer like
FTP, Hightail, Google Drive or Dropbox.

• If the client is providing us with a database instance we will require full DB Admin rights to the
Conversation Hub database instance.

Technical Overview Of The Conversation Hub