| |
Login To The TeamTrack
Evaluation Sample
For a more effective evaluation, and to get you thinking about
how you work — we've listed various roles within most organizations.
By logging in as any of these roles, you'll see an example of
how TeamTrack is utilized within that area. Note: Don't forget
that TeamTrack is fully customizable and can be modified to meet
your business needs.
Get started now by logging onto this TeamTrack evaluation
using any of the following Login IDs. No password is required.
Management Roles:
|
| Carmen is Chief Officer who has a home page
displaying numerous high level reports in a management dashboard portal. Use this
login ID to see a variety of different report types.
|
|
|
Role:
Upper-Level
Management
|
|
| A manager having extensive privileges in
the Defect and Issue Management solution, including privileges to transition
any issue in the Issues-based projects. As a manager, Joe also has privileges
in the Human Resources solution. Use this login ID to evaluate TeamTrack’s
multi-view reporting capabilities.
|
Defect and Issue Management Roles:
|
| An
engineer who has chosen the "Folders" home-page
view in their User Profile. Use this login to see how "Folders" can
be set up to provide quick, intuitive access to a wider
set of issues. |
|
|
Role:
Engineer with Limited Access
|
|
| As a developer who works primarily
in the Defect and Issue Management solution, Newton can work in the
Software Development and Hardware Manufacturing project hierarchies.
Notice that when Newton clicks the Submit icon, she can only submit
into these projects. Use this login ID to evaluate TeamTrack's issue
management capability. |
|
| Chris is a tester who, like Newton,
primarily works in the Defect and Issue Management solution. Use this login
ID to see how issues move through the testing cycle.
|
Support Center Roles:
|
|
Role:
Support Center Manager
|
|
| As a Support Center manager, Tom
primarily uses the Support Center solution. He also has limited
privileges to the Defect and Issue Management solution, enabling him
to submit and view items into Issues-based projects. Tom's home page
in the Support Center solution shows all incidents by project and
owner, allowing him to easily determine the workload of support
technicians.
|
|
|
Role:
Level One Support Technician
|
|
| As a level-one support technician, Chad’s
home page report displays a list of all the calls he owns. Chad’s primary
job is to answer those questions he can, and assign the remaining to another
support technician. Chad can also search for customers, add new customers, search
the knowledgebase, run reports, and submit new incidents.
|
|
|
Role:
Level Two Support Technician
|
|
| A
level-two support technician. Ethan’s job is to answer
questions that Chad cannot, so Ethan’s home page shows
all incidents assigned to him. Ethan has the same access
privileges as Chad.
|
|
|
| As an external customer, Frank
can view the status of incidents he submitted and that were
submitted by others in his company. Frank can also search for
problems and resolutions in the Knowledge Base.
|
|
|
 |
LOGIN HELP
1. Click
here to pop-up the authentication
dialog box.
2.
Type the Login ID (i/e Joe) of the Role you
would like experience.
3.
No password is required.
|
|
|
 |
|
Login
To TeamTrack
