Table of Contents
The current Web page and AGTEK Access authentication is two separate systems with different passwords. This is not only a mediocre user experience with confusion but it also doesn't allow us to capture usage numbers for support by user within a company, allow the user to reset their own password, and encourage them to let our emails through their filters. Add to that is also discourages the use of “Field user 1” as users and lays the groundwork for payment systems and provisioning.
Changes to the Corporate Web Site
Chief among the changes is a profile control in the upper right. There's several elements to this shown in the graphics below as logged in:
The menu when clicked
When in not logged in state and login is clicked
Currently a successful login sets a session variable, reads the username and displays it. Selecting logout from the menu clears that session variable. Trying to access protected content currently displays another login page that remembers what page the user was trying to get to but asks for the login. Once there is a successful login the user is forwarded to the remembered page.
The page currently looks like this but can be changed to be more in line with what we are currently offering.
Profile Page
The user profile is accessed by select profile. This is where he can change most values except for the actual login, reset his password and see which AGTEK keys he's on along with their products on them.
Note: Screen updated to make better use of horizontal space and make the login visually noneditable.
Sample CSS for reference https://agtek.s3.amazonaws.com/Agtek/X98c0HXmQtRV
Corporate Web & Apps Server Integration
Part of the goal is to reduce logins to just one that matches for both keys and the support information. These websites technically exist on different servers and will probably remain that way. In order to minimize the visible change to the user we've added Apps to the Corporate Web page and ideally a successful authentication means that the user is not forced to login again when going between servers. We will also try to maintain a similar look and feel and ideally they will not even know they have switched sites except for being on a different subdomain and submenus.
Needed Functions
I think these are new.
Forgotten password reset method
A forgotten password method in the pattern of email/reset as is commonly done on most websites. We do not currently have email addresses for most users as the field did not exist. We may want to see about executing a one-off population of that field when the current login has an email address pattern.
Cross authentication
Between the two different websites and possibly from application to website for help/help videos without logging in again.
