Getting started with TDX Foundations

This getting started article will help TeamDynamix Administrators to get oriented with TeamDynamix and the three interfaces: TDAdmin, TDNext, and TDClient. The user must have administrator permissions within TDAdmin.


The TeamDynamix (TDX) Foundations module covers the core TeamDynamix configuration that all implementations should consider: Account and department records, Briefcase integrations, days off, security roles, notifications, groups, users, and security roles.

This module also introduces the different interfaces: TDAdmin for administration, TDNext for people working on tickets or projects, TDClient for end users, as well as the web API.


The foundations module will cover the basic purpose for the three TeamDynamix interfaces. TDAdmin, TDNext, and TDClient. You will also learn how to manually create a user from the TDAdmin interface. As well as set up basic Security Roles. You also receive a high level overview of setting up, and how to create Account Departments and Location rooms and how they are used in the system. There will also be a first look at core integrations, such as APIs, email service, and authentication in this module.


Where to Find This

This article covers features that appear in the TDAdmin and TDNext interfaces.

These features can be accessed following these paths:

  • TDAdmin
    • Licenses
    • Administrators
    • Notification Templates
  • TDAdmin > Organization Settings
    • Accts/Depts
    • Account Attributes
    • Briefcase/Attachment Integration
    • Days Off
    • Locations
  • TDAdmin > Users & Roles
    • Attributes
    • Groups
    • Security Roles
    • Users
  • TDNext
    • Community
    • Help

Where to Start

In TDX Foundations, an institution should:

  • Decide who will be the TDX administrators.
  • Decide when to work in the sandbox vs. when to work in production.
  • Define their account or department records and/or load a couple of example records.
  • Turn on Briefcase (attachment) integrations.
  • Configure days off and make a note (or a scheduled ticket) to create days off records each year.
    • Scheduled tickets are covered in the Advanced Ticketing Module
  • Define their location records and room records.
  • Identify whether they might want notification footers. If you are using ticketing applications, you will also need to do this for each ticketing application.
  • Define a couple of initial security roles.
  • Ensure user records exist for the TDX project team.

Example Security Roles

Over time you will add more security roles. TeamDynamix recommends starting out with very few security roles and adding to them.

  • Client – End users; these are members of your organization who will access the Client Portal to submit Service Requests or search your Knowledge base
  • Enterprise/System Admin – TeamDynamix administrators with full access to the system and all the applications
  • Technician – TDNext only users

Gotchas & Pitfalls

These are module-specific issues that may affect how quickly you can get it implemented:

  • Defining the list of acct/dept records to load can be challenging for some institutions.
  • Defining the list of location records to load can be challenging for some institutions.
  • Trying to create too many security roles when first learning the tool can slow down an implementation. You can create additional security roles at any point so don’t get hung up on this.

Also have a look at the TDX Foundations Frequently Asked Questions.



Article ID: 30217
Thu 5/11/17 6:23 PM
Wed 5/25/22 1:42 PM