Who can use this feature?
- Protected custom attributes and their logs are managed in TDAdmin
- License Requirement: Enterprise
- Administrative Access: User must be a Global Administrator with the org-level-admin permission, Can Create/Modify Attribute Protections
Protected custom attributes (PCAs) allow administrators to secure sensitive data in TeamDynamix by controlling who can view and edit specific custom attributes on tickets, assets, configuration items, issues, or risks. This article covers what PCAs are, their limitations, and how to configure, manage, and audit them.
In this article, we'll cover:
Where to Find This
In TDAdmin, navigate to the log for your application:
- Ticketing applications: Applications > [Ticketing application] > Protected Attribute Access Log or Protected Attribute Configuration Log
- For global Ticketing application and app-level attributes: TDAdmin > Ticket Custom Attributes > Attributes
- Asset/CI applications (assets and configuration items): Applications > [Asset application] > Custom Attributes > Protected Attribute Access Log or Protected Attribute Configuration Log
- Project applications (issues and risks): Applications > [Project application] > Custom Attributes > Protected Attribute Access Log or Protected Attribute Configuration Log
Custom attributes on tickets, assets, configuration items, issues, or risks can be marked as "Protected," which restricts their content from unauthorized viewing. When you enable the Protected flag on a custom attribute, it becomes a Protected Custom Attribute (PCA).
PCAs provide enhanced security through:
- Permission-based visibility – Only users in authorized groups can view the attribute
- Audit logging – Every view and edit is logged with timestamp, user, IP address, and value at time of access
- Partial masking – Option to show only part of the value (for example, the last 4 digits of an SSN)
- PIN authentication – Optional additional security requiring users to enter their PIN before viewing
Before implementing PCAs, understand these security-driven restrictions:
Configuration
- Only new custom attributes can be protected; existing attributes cannot be converted to PCAs
- PCAs cannot be the driver for attribute dependencies
- When a PCA is the child of a dependency, the protected attribute icon is hidden after creation for users without access to the protected attribute.
- Protected attributes cannot be unprotected once created
- Protected attributes cannot be converted to global attributes or merged into global attributes
- PCAs cannot be deleted once created
Operations
- PCAs are excluded from email notifications
- PCAs are excluded from AI Ticket Summaries
- PCAs cannot be added to Ticket Templates
- PCAs cannot be imported using ticket or asset import tools
- Users without permission for a PCA can create items with the PCA filled in, but they cannot view or edit those values later
- Changes to PCAs are not shown in detail in the feed. If only PCAs change as part of an edit, the feed entry reads “Edited this [item]”
Reporting and Analysis
- PCAs cannot be included in Reports or Dashboards
- PCAs cannot be used as search filters
- PCAs are excluded from the TeamDynamix Web API
All users, including Global Administrators, must be in a group with permission for a specific PCA to see or interact with it.
Viewing Protected Attributes
When a user views an item in Work Management (TDNext) containing PCAs:
- If the user has permission, they will see the custom attribute on the item
- Each PCA value is hidden behind an eye icon ()
- Clicking the eye icon reveals the value
- The system logs the view event with user, timestamp, IP address, and the value viewed
- Users without permission will not see the eye icon at all
Editing Protected Attributes
When a user edits or updates items with PCAs:
- Protected fields remain hidden until the user clicks the eye icon
- After viewing, the field becomes editable
- Editing the PCA value creates two separate log entries: one for viewing and one for editing
- Users without permission cannot view or edit the attribute
Partial Masking
PCAs support partial masking to show limited information while keeping the full value protected. You set the number of characters to unmask, counting from the end of the value, and users without full permissions see only those characters. For example, unmasking 4 characters of a Social Security number displays *****1234.
Masking options are available only for Textbox attributes with a Text, Integer, or Decimal data type.
When viewing items with masked PCAs:
- Users without full permissions see only the unmasked portion
- Users with full permissions see the complete value
PIN Authentication
For highly sensitive data, you can require PIN authentication:
- Users must enter their PIN before viewing the attribute
- This adds an extra verification layer beyond group membership
- If a user forgets their PIN, an administrator can reset it using the Reset PIN option in the Actions menu on the user.
To configure PCAs and open their logs, a Global Administrator needs the Can Create/Modify Attribute Protections permission.
Note: This permission allows a Global Administrator to create and modify attribute protections and to open the Protected Attribute Access Log and Configuration Log. The Access Log can reveal PCA values. This permission does not, by itself, display a PCA’s value on an item in Work Management. The administrator must also belong to a group with permission for that attribute. Grant this permission only to trusted administrators who need to configure sensitive data protections.
To assign permission to configure PCAs:
- In TDAdmin, click Home, then the organization name at the very top of the left navigation (the item above "Organization Settings").
- Click the Administrators tab.
- Click the name of the user whose permissions you need to edit.
- Check the Can Create/Modify Attribute Protections checkbox.
- Click Save.

PCAs can only be defined by global admins when creating a new attribute; existing attributes cannot be protected after the fact. Once created, protected custom attributes cannot be deleted.
- In TDAdmin, navigate to the appropriate Attributes page following the paths in Where to Find This above.
- On the Attributes page, click +New.
- Fill in the standard attribute fields (name, label, type, etc.).
- At the bottom of the form, check the Protected checkbox. This makes the attribute a PCA. The Client Visible checkbox will be disabled (see the next section for client visibility options).
- Click Save.
Note: Application administrators can view the settings of existing application-level protected custom attributes, but they cannot create PCAs. Ticketing application Admins cannot view or edit global attributes, including global PCAs, in the Admin interface.
After saving, additional options and tabs will appear. On the General tab, scroll down to the Protected Configuration section and configure the protection settings:
- Always allow requestor to view data in Client Portal – Enables the requestor to view this attribute in the Client Portal, even if they wouldn't normally have permission.
- Require technician to enter PIN to access data – Forces users to enter a PIN before viewing the value. For more information on PIN settings, see Working with Personal Identification Numbers (PIN).
- Masking Options
- Number of characters to unmask – The number of characters, counted from the end of the value, that automatically display without requiring users to enter a PIN (for example, 4 displays
*****1234).
- Number of seconds to display values – The number of seconds an unmasked value remains visible before it is automatically masked again.
Click Save after configuring these settings.
Protected custom attributes are visible in Work Management only to users who belong to authorized groups. This applies to all users, including Global Administrators. Without group permissions, the PCA remains masked to everyone.
- In TDAdmin, on the attribute's edit page, click the Permissions tab
- Click the Add Associated Groups field to select the group(s) that should have access
- Click Add
Important: You must associate at least one group, or the PCA will remain completely masked, even when you try to unlock it with a PIN. The PIN eye icon only appears when group permissions are set.

Protected custom attributes are added to Forms in the same way as regular custom attributes, with these considerations:
- When you add a PCA to a form, the Protected icon (crossed-out eye) displays next to the attribute
- Clicking the icon will provide a summary of the PCA’s settings, including which groups can view it
- PCAs cannot be marked as "Hidden" or "Read-Only" for Work Management users

TeamDynamix keeps two logs for PCAs. Each application with PCAs has its own set, and the Ticket Custom Attributes section in TDAdmin has a combined set for all ticket PCAs, global and application-level. Global Administrators with the Can Create/Modify Attribute Protections permission can open them in TDAdmin:
- The Access Log records each view and edit of a PCA, including the date, access type, user, item, values, and IP address.
- The Configuration Log records changes to the PCA’s settings, such as groups added, PIN requirement changes, and visibility duration changes.
You can open both logs from the Access Log and Configuration Log tabs on a PCA’s edit page, or from the application’s Protected Attribute Access Log and Protected Attribute Configuration Log pages. To review all Ticketing app-level and global PCA logs in one place, open TDAdmin > Ticket Custom Attributes > Protected Attribute Access Log or Protected Attribute Configuration Log.
Warning: In the Access Log, the Old Value and New Value fields are hidden by default. Anyone who can open the log can select Show attribute values to display them, and that action is not logged. Exporting the log To Excel also exposes the values.
For details, see Viewing Protected Attribute Logs.