Body
Intended Audience: Administrators
This article is intended for Administrators. This article may be public, but intended for specific roles. If this article does not suit your needs, please leave feedback or locate a related article as previously directed.
Outgoing and incoming email settings may be configured at the ticketing application level. These settings dictate how TeamDynamix responds to incoming emails your ticketing application receives and how it sends emails to your customers.
Outgoing and incoming email settings are configured globally. Applications may deviate from these global settings for logging purposes if necessary.
The most common email configurations pertain to email monitors and email reply monitors. These monitors create tickets from emails specified by the application's settings and update ticket feeds from received emails.
For information on configuring email monitors, please see the Email Integration guide. To request email integration creation, please get in touch with your application administrator or submit a request to the TeamDynamix Administration catalog.
Email Conventions
The ticketing application administrator primarily determines the configuration of email settings. As such, there exist no mandates for specific designs or methodologies.
However, all emails connected to TeamDynamix must be on the UNLV domain (@unlv.edu) and must have the following naming convention:
- Email name:
- [NAME] Automated Ticketing Response
- For example: Administration Automated Ticketing Response
- Email address:
- [NAME].notifications@unlv.edu
- For example: administration.notifications@unlv.edu
Grandfather Clause
For applications that have implemented an email monitor, changes to comply with these policies are recommended but not requred.
A list of applications is maintained by the Business Affairs TeamDynamix administrator. Please contact Naseem.Benjelloun@unlv.edu if you have questions about the applicability of this clause.