Objective
To request additional permissions be added or removed for a user in TeamDynamix (TDX).
Before You Begin
Verify you know what roles will be needed for each application of TDX.
Please Note: Some roles are only available to specific teams, so if you request them for individuals that do not meet the requirements, your request may be rejected.
Overall Roles
Every user will need to start with an overall role. This role will determine which applications and application roles are available. All users will have the Client role by default. The roles available are:
Role Name |
Description of Role |
Intended Audience |
Access Management |
Role for members of the Access Management team to allow updating of user permissions and group memberships. Allows access to all TDX interfaces. |
Access Management |
Analyst |
Default access granted to most analysts/technicians. Allows access to both the Client Portal (TDPortal) and Users (TDNext) interfaces. |
Any users who need additional permissions within any component of TeamDynamix |
Client |
Default access granted to all non-technician users. Only allows access to the Client Portal (TDPortal) interface. |
All users without additional permissions |
Discovery Services |
Role for members of the Discovery Services team to allow permissions necessary for legal compliance. Allows access to both the Client Portal (TDPortal) and Users (TDNext) interfaces. |
Discovery Services |
Manager |
Role for managers that includes the permissions of Analyst with additional permissions within projects, resource management, and analysis. Allows access to both the Client Portal (TDPortal) and Users (TDNext) interfaces. |
Managers of Analysts |
Portfolio & Project Management |
Role for select members of Portfolio & Project Management to allow functional administration of TDX. Allows access to both the Client Portal (TDPortal) and Users (TDNext) interfaces. |
EPMO or IT Services Strategy & Planning Administrators |
Project Manager |
Role for Project Managers to allow administration of projects in TDX. Allows access to both the Client Portal (TDPortal) and Users (TDNext) interfaces. |
EPMO or IT Services Strategy & Planning |
Service Management |
Role for members of the Service Management Office to allow functional administration of TDX. Allows access to both the Client Portal (TDPortal) and Users (TDNext) interfaces. |
Service Management Office |
System Administrator |
System Administrator access only granted to members of Vended Products and CRM who are supporting TDX. Allows access to all TDX interfaces. |
Vended Products and CRM |
Unit Application Administrator |
Role for members of units with individual TDX applications to allow functional administration of those applications |
Application administrators in non-IT units with TDX separate applications |
All non-Client roles will grant access to the Users (TDNext) interface. Within this interface, there are many applications available. The overall role will determine which applications (also referred to as tabs or components) the user will be able to access.
- Analysis: Analysis provides the tools to generate reports and analyze the organization's portfolio from any angle. The data is pulled directly from projects, tickets, requests and resources throughout the TDNext solution. This application functions like the Reports feature within the individual component applications, but allows you to select from all report types. It will not allow you to combine fields from different report types or add any additional calculation or group capabilities.
- Community: The Community application gives users a direct link to the TeamDynamix Community through secure integration in the TDNext application menu. The TeamDynamix Community is home to the TeamDynamix User Groups.
- File Cabinet: The File Cabinet application allows users to archive files from projects or workspaces and view files after those projects have been closed.
- My Work: The My Work application gives TDNext users a unified view of their assigned tickets, tasks, approvals and other work items.
- News: The News application allows users to consume RSS feeds within TDNext.
- People: The People application allows users to search, create, and modify People and Account/Department records in TDNext.
- Project Templates: The Project Templates application allows users to create templates for projects and workspaces, which can include briefcase files, contacts, links, project plans and issues, which can then be applied to new projects and workspaces.
- Projects: The Projects application allows users to work with projects within TDNext.
Below is a table that illustrates the relationship between the role and applications.
Application |
Access Mgmt |
Analyst |
Discovery Services |
Manager |
Portfolio & Project Mgmt |
Project Manager |
Service Mgmt |
System Admin |
Unit App Admin |
Analysis |
|
|
|
x |
x |
x |
x |
x |
x |
Community |
x |
x |
x |
x |
x |
x |
x |
x |
x |
File Cabinet |
x |
x |
x |
x |
x |
x |
x |
x |
x |
My Work |
x |
x |
x |
x |
x |
x |
x |
x |
x |
News |
x |
x |
x |
x |
x |
x |
x |
x |
x |
People |
x |
x |
x |
x |
x |
x |
x |
x |
x |
Project Templates |
|
|
|
|
x |
x |
|
x |
|
Projects |
x |
x |
x |
x |
x |
x |
x |
x |
x |
Primary Application Roles
There are also applications that require a specific application role be specified to be able to access them. The Primary Applications are the central applications that are used by the majority of users.
Primary Client Portal Roles
The Client Portal role determines the permission level for items in the Client Portal, including Service Catalog and Knowledge Base. The Client Portal is an application that allows clients to access self-service offerings and track requests.
Role Name |
Description of Role |
Intended Audience |
Overall Role Required |
Analyst |
Default access granted to most analysts/technicians |
Any users who need additional permissions |
Any Non-Client Role |
Client |
Default access granted to all non-technician users |
All users without additional permissions |
Client |
Knowledge Analyst |
Role for members of the Knowledge Management group to assist with administering the Knowledge Base |
Service Management Office Student Employees |
Any Non-Client Role |
Service Desk |
Role for members of the MSU IT Service Desk to allow some additional permissions in the Client Portal |
MSU IT Service Desk |
Any Non-Client Role |
Service Management |
Role for members of the Service Management Office to allow functional administration of the Client Portal |
Service Managmenet Office |
Service Management |
System Administrator |
System Administrator access only granted to members of Vended Products and CRM who are supporting TDX |
Vended Products and CRM |
System Administrator |
Primary Tickets Roles
The Tickets role determines the permission level for the Tickets application in the TDNext interface. The Tickets application allow users to view and edit tickets, tasks, and other related items.
Role Name |
Description of Role |
Intended Audience |
Overall Role Required |
Analyst |
Default access granted to most analysts/technicians |
Any users who need additional permissions |
Any Non-Client Role |
Manager |
Role for managers that includes the permissions of Analyst with the ability view survey responses and other analytics |
Managers of Analysts |
Manager |
Service Desk Analyst |
Role for members of the MSU IT Service Desk includes the permisions of Analyst with the ability to use all ticket forms |
MSU IT Service Desk |
Any Non-Client Role |
Service Desk Manager |
Role for the Service Desk Manager that includes the permissions of Service Desk Analyst with the abilityto view survey responses |
MSU IT Service Desk Leaders |
Any Non-Client Role |
Service Management |
Role for members of the Service Management Office to allow functional administration of the Tickets application |
Service Management Office |
Service Management |
System Administrator |
System Administrator access only granted to members of Vended Products and CRM who are supporting TDX |
Vended Products and CRM |
System Administrator |
Primary Assets/CIs Roles
The Assets/CIs role determines the permission level for the Assets/CIs application in the TDNext interface. The Assets/CIs application allows users to easily view assets, configuration items, vendors, contracts, and locations allowing an organization to track and maintain hardware and software assets, in addition to other configuration items, cost-effectively.
Role Name |
Description of Role |
Intended Audience |
Overall Role Required |
Analyst |
Default access granted to most analysts/technicians |
Any users who need additional permissions |
Any Non-Client Role |
Service Management |
Role for members of the Service Management Office to allow functional administration of Asset/CIs |
Service Management Office |
Service Management |
System Administrator |
System Administrator access only granted to members of Vended Products and CRM who are supporting TDX |
Vended Products and CRM |
System Administrator |
Project Requests Roles
The Project Requests role determines the permission level for the Project Requests application in the TDNext interface. The Project Requests application allows users to view, edit, and approve project requests submitted via the Client Portal.
Role Name |
Description of Role |
Intended Audience |
Overall Role Required |
Portfolio & Project Management |
Role for select members of Portfolio & Project Management to allow functional administration of TDX |
EPMO or IT Services Strategy & Planning |
Portfolio & Project Management |
Project Manager |
Role for Project Managers to allow administration of projects in TDX |
EPMO or IT Services Strategy & Planning Administrators |
Project Manager |
System Administrator |
System Administrator access only granted to members of Vended Products and CRM who are supporting TDX |
Vended Products and CRM |
System Administrator |
Unit Application Roles
Some non-IT units have their own TDX applications on https://tdx.msu.edu, these applications also require a role be specified to be able to access them. Unit applications have standardized roles and access requests for these applications will be routed to the department for approval.
Unit Client Portal Roles
Role Name |
Description of Role |
Intended Audience |
Overall Role Required |
Analyst |
Default access granted to most analysts/technicians |
Any users who need additional permissions |
Any Non-Client Role |
Client |
Default access granted to all non-technician users |
All users without additional permissions |
Client |
Application Administrator |
Role for members of units with individual Client Portal applications to allow functional administration |
Application administrators in non-IT units |
Unit Application Administrator |
System Administrator |
System Administrator access only granted to members of Vended Products and CRM who are supporting TDX |
Vended Products and CRM |
System Administrator |
Unit Tickets Roles
Role Name |
Description of Role |
Intended Audience |
Overall Role Required |
Analyst |
Default access granted to most analysts/technicians |
Any users who need additional permissions |
Any Non-Client Role |
Manager |
Role for managers that includes the permissions of Analyst with the ability view survey responses and other analytics |
Managers of Analysts |
Manager |
Application Administrator |
Role for members of units with individual Tickets applications to allow functional administration |
Application administrators in non-IT units |
Unit Application Administrator |
System Administrator |
System Administrator access only granted to members of Vended Products and CRM who are supporting TDX |
Vended Products and CRM |
System Administrator |
Unit Assets/CIs Roles
Role Name |
Description of Role |
Intended Audience |
Overall Role Required |
Analyst |
Default access granted to most analysts/technicians |
Any users who need additional permissions |
Any Non-Client Role |
Application Administrator |
Role for members of units with individual Assets/CIs applications to allow functional administration |
Application administrators in non-IT units |
Unit Application Administrator |
System Administrator |
System Administrator access only granted to members of Vended Products and CRM who are supporting TDX |
Vended Products and CRM |
System Administrator |
Steps
This request will be automatically provisioned once it has been approved. This allows for faster access updates, but will not factor in any comments and will not allow for "mirroring requests" that ask for access to match another individual.
- From the Access Management service, select the Request button for the TeamDynamix (TDX) access request or from the TeamDynamix (TDX) Access service offering, select the Request TeamDynamix (TDX) Access button.
- Search for and select the individuals you are looking to update the access for.
- You can grant multiple individuals access on one request, as long as each is getting the same access.
- Select the roles needed for each application.
- If access is not needed to a specific application, then you can update the drop-down option for that application to No Action.
- You can also use the Select Primary Application Defaults to select the default role for all primary applications at once.
- By default, the primary applications are displayed. They can be hidden by changing the selection on the Show Primary Applications switch. Unit applications can be displayed by changing the selection on the Show Unit Applications and selecting the appropriate unit from the dropdown list.
- This form will also allow you to request additional items for the users:
- The Group Membership option on the form allows you to specify group memberships. After selecting an action, the left-hand list will populate with a list of groups. Select a group from the list and click the >> button to move the selection to the right-hand list.
- The Search for Groups option can be used to filter the groups in the left-hand list. To remove the filter, you can use the red Clear button.
- By default, notifications are enabled, however, you can change the Include User in Group Notifications option to No before adding a group to the list to disable the notifications.
- If you would like to change the notification setting on a group you already added to the selection list, remove the group and add it again with the proper notification setting selected.
- It is recommended that users have a Primary Group selected to aid in visibility of tickets. To update or set the primary group, change the Upgrade Primary Group option to Yes and then select the appropriate list from the drop-down. Only groups in the selection list on this form will be listed.
- The Desktop Templates option on the forms allows you to specify additional desktop templates to be granted to the users. After selecting an action, the left-hand list will populate with a list of desktop templates. Select a desktop template from the list and click the >> button to move the selection to the right-hand list.
- By default, all non-client users will be granted the Technician Desktop (2 Column) and Technician Desktop (3 Column) desktop templates.
- Some desktop templates are only available to members of specific teams or individuals with specific roles
- Add your response to the Business Needs / Comments field.
- Select the Check Form button to validate the form and address any errors.
- Select the Submit Access Request button to submit the request.
Additional Info