Editing User Applications

This how-to article will help TeamDynamix Administrators to manage their user’s application access using TDAdmin. The user must have Administrator privileges within TDAdmin to perform these steps.

Overview

Managing a user’s application access is different than managing their security role.

Manually Editing User's Applications in TDAdmin

Editing a User’s Applications in TDAdmin

To edit the applications for a user in your organization:

1. In TDAdmin, navigate to Users & Roles > Users.
2. Click the Name of the user your wish to edit in the list.
3. On the User Profile page, click the Applications tab.
4. Make any necessary changes. Common changes include:
   1. Selecting the box next to an application, to grant access
   2. Unchecking the box next to an application, to remove access
   3. Changing the license type of a user to restrict or enable access within a current application
   4. Selecting the “Admin” box to make the user an Administrator of the app within TDNext
5. Click the Save button.

Editing Multiple User's Applications in TDAdmin

To edit the applications for multiple users in your organization: 

1. In TDAdmin, navigate to Users & Roles > Users.
2. Select the boxes for all users you wish to edit in the list.
3. Click the Actions button.
4. Choose Add Applications. 
5. Select the boxes for all applications you wish to grant those users access to. 
6. Click the Save button.

Applications can also be changed via the TeamDynamix API.

Editing User's Applications via TDWebApi People Import File

To edit the applications for users in your organization on the People Import File, be sure to include the 'Allow Security Role Changes' and 'Allow App Access Change' flags on the import call/utility command line.

Editing User's Standard Applications on the People Import File

1. Add a column to the import sheet for the application with a header like: Has*Application*
   1. For example, to edit application access for TDNext, add a column with the header: HasTDNext
2. To grant application access for a user, set the value for the Has*Application* column to True.
3. To remove application access for a user, set the value for the Has*Application* column to False.

Editing User's Asset Applications on the People Import File

1. Add a column to the import sheet for the asset application with a header like: TDAssets-*ApplicationID*
   1. For example, to edit application access for asset application 1234, add a column with the header: TDAssets-1234
2. To grant asset application access for a user, set the value for the TDAssets-*ApplicationID* column to specify a security role name for the application which matches its name in the system exactly, including correct capitalization.
3. To remove asset application access for a user, simply specify a blank value for the TDAssets-*ApplicationID* column.

Editing User's Client Portal Applications on the People Import File

1. Add a column to the import sheet for the client portal application with a header like: TDClient-*ApplicationID*
   1. For example, to edit application access for Client Portal 1234, add a column with the header: TDClient-1234
2. To grant Client Portal application access for a user, set the value for the TDClient-*ApplicationID* column to specify a security role name for the application which matches its name in the system exactly, including correct capitalization.
3. To remove Client Portal application access for a user, simply specify a blank value for the TDClient-*ApplicationID* column.

Editing User's Ticketing Applications on the People Import File

1. Add a column to the import sheet for the ticket application with a header like: TDTickets-*ApplicationID*
   1. For example, to edit application access for Ticket Application 1234, add a column with the header: TDTickets-1234
2. To grant ticket application access for a user, set the value for the TDTickets-*ApplicationID* column to specify a security role name for the application which matches its name in the system exactly, including correct capitalization.
3. To remove ticket application access for a user, simply specify a blank value for the TDTickets-*ApplicationID* column.

A full list of application specific column headers for the import file can be found in TDAdmin > Users & Roles > Import Jobs > Help Button.

Examples

A lead member of a help desk team may need special access to the Projects & Workspaces application for project management.

A project manager may need access to the Tickets or Analysis application to get an overview of a resource’s workloads.