\n
![\"Extensive](\"https:\/\/www.topdesk.com\/en\/wp-content\/media\/sites\/30\/task-board-extensive-changes-overview.png\")
<\/a>\nThe updated Task Board displays the extensive changes you manage alongside your other tasks. You\u2019ll see:<\/p>\n
- \n
- A clear overview of all extensive changes, including how much time is left until the planned implementation date.<\/li>\n
- Direct links to underlying activities within each extensive change. Click on the extensive change to open the preview panel. You\u2019ll find a list of all activities on the General tab. This way, you get immediate input on how the change is progressing, and if action is needed to realize the planned implementation date.
\n![\"Extensive](\"https:\/\/www.topdesk.com\/en\/wp-content\/media\/sites\/30\/task-board-extensive-changes-activities.png\")
<\/a><\/li>\n<\/ul>\nExtensive changes on TOPdesk Mobile<\/h3>\n
In addition to the Task Board of TOPdesk\u2019s desktop version, we made the same improvements to TOPdesk Mobile. So, if you\u2019re always on the move, you’ll stay up to date on all extensive changes you manage.<\/p>\n
For more information about extensive changes on TOPdesk Mobile, see our documentation portal<\/a>.<\/p>\n
Self-Service Portal: a new look for Knowledge Items and Service pages<\/h2>\n
Three important Self-Service Portal pages have received a fresh look: the Service page, the Knowledge Base overview page, and the Knowledge Item card<\/strong>.
\n![\"\"](\"https:\/\/www.topdesk.com\/en\/wp-content\/media\/sites\/30\/ssp-service-card-1.png\")
<\/a>
\nWe applied our updated design standards to these pages, with which we pay extra attention to accessibility and responsiveness<\/a>. You might have noticed that all flows linked to a Service page are now listed under Further options. Showing a header text for each section helps with making the page more accessible for every user.
\n![\"'Go](\"https:\/\/www.topdesk.com\/en\/wp-content\/media\/sites\/30\/ssp-KI-banner.png\")
<\/a>
\nOn the Knowledge Item card, you\u2019ll find similar changes. Knowledge Items that are under the opened Item in your Knowledge Base\u2019s structure are listed in the Further actions section. Also, you can easily find your way back to a Service page with the new navigation banner on top.<\/p>\nYou might also notice that the button to copy the URL of a Knowledge Item has been removed. Instead, simply copy the URL from the URL bar of your browser to share a direct link to the item.
\n![\"New](\"https:\/\/www.topdesk.com\/en\/wp-content\/media\/sites\/30\/kb-page.png\")
<\/a>
\nAnd finally, the Knowledge base overview page for the SSP updated in a similar way. The various branches of your Knowledge base, now also known as folders, are shown in blocks instead of columns. To avoid some blocks becoming too large, they show a maximum of 10 items.<\/p>\nOne TOPdesk User: more bulk linking criteria and new API account card<\/h2>\n
As part of our One TOPdesk User<\/a> project, we released two important additions to Supporting Files.<\/p>\n
More ways to match operators and persons<\/h3>\n
In the previous update, we introduced the bulk linking wizard to help you link Operator cards to Person cards<\/a>. It automatically matches cards based on their login name, making it easier for you to prepare for the One TOPdesk User milestones. Now, we\u2019ve expanded the matching criteria to five TOPdesk fields:<\/p>\n
- \n
- Email address<\/li>\n
- Employee number<\/li>\n
- Network login name<\/li>\n
- Mainframe<\/li>\n
- Login name<\/li>\n<\/ul>\n
To match your Operator and Person cards, simply pick the field that has the same value on both cards.<\/p>\n
Remember the milestones<\/h3>\n
Keep these important dates for the One TOPdesk User project in mind:<\/p>\n
- \n
- From 1 November 2025<\/strong>: New Operator cards must be linked to a Person card.<\/li>\n
- Mid-February 2026<\/strong>: All Operator cards must be linked to a Person card. After this date, any unlinked Operator cards will get linked to an automatically generated Person card, which could lead to duplicate cards and a loss of incident history.<\/li>\n<\/ul>\n
A new way of managing API accounts<\/h3>\n
With the important changes of the One TOPdesk User project in mind, and to improve the general usability of API accounts, we introduced the new API account card. Before, API accounts were regular Operator cards that were marked to be used specifically for automations and integrations. You can\u2019t use them to log in to the Operator section interface: you only use them to access your TOPdesk via API requests. A benefit of these API accounts is that they don\u2019t use operator licences, even when they extensive permissions.
\n![\"New](\"https:\/\/www.topdesk.com\/en\/wp-content\/media\/sites\/30\/api-accounts.png\")
<\/a>
\nBecause it often makes no sense to link an API account to a Person card, and the button to manually create an Operator card was recently removed, we added a new API Account button to the Supporting Files module page. This way, you can still create an API account easily without linking it to a person.<\/p>\nOn the new API account card, you\u2019ll find a few important differences to the regular Operator card:<\/p>\n
- \n
- The TOPdesk Login section only contains a Login Name<\/strong> field, but not a field for a password. Since authentication is only done via an application password, the regular password has no value for API accounts.<\/li>\n
- An Application passwords<\/strong> section. For regular Operator cards, you still find this in My Settings. This move means that you, as the application manager, don\u2019t need to log out and log in all the time to add new application passwords to an API account.<\/li>\n<\/ul>\n
All Operator cards that were already marked as API accounts are automatically converted to a new API Account card. Existing application passwords are moved to the new \u2018Application passwords\u2019 section.<\/p>\n
If you want to manually change a regular Operator card to an API Account card, you need to create a new API Account card. Keep in mind that you will have to create new application passwords on this card, and therefore also must update these in your automations and integrations.<\/p>\n
For an extensive read about this new API Account card in TOPdesk, see knowledge item KI 18706 on My TOPdesk<\/a>.<\/p>\n
Coming soon to Incident Management: copy and paste images into your incidents<\/h2>\n
The saying \u2018A picture is worth a thousand words\u2019 might be a little overused, but it definitely holds true for service requests. While explaining your problem with words might add to the confusion within your service team, a picture often gives plenty of clues for how to solve a problem.<\/p>\n
In October, we started the release of a long-awaited change for Incident Management: the ability to add inline images to Incident card conversations by simply pasting them.
\n![\"Paste](\"https:\/\/www.topdesk.com\/en\/wp-content\/media\/sites\/30\/richtext.png\")
<\/a>
\nPasting images is part of the updated Rich Text editor in Incident Management. With this release, the new editor and the ability to paste images directly into your message is available for the Operator section. The new editor was first released for TOPdesk test environments mid-October. The feature is rolling out to production environments over the coming weeks. When this part of the release is done, the feature is made ready for the Incident card on the Self-Service Portal.<\/p>\nUpdate your automated actions<\/h3>\n
Once the new editor is available in your environment, TOPdesk will use an updated Incident Management API. As a result, you might need to make some changes to your actions and integrations. This specifically concerns actions that request progress trail entries with images via the API.<\/p>\n
For more information about the changes in the Incident Management API and how to update your actions, see KI 18044 on My TOPdesk<\/a>. In KI 18723<\/a>, you\u2019ll find more details about this functionality.<\/p>\n
Automated Actions: Create more personal and informative notifications<\/h2>\n
In Automated Actions, basically all relevant information is accessible as long as you request it first with an HTTP step. We\u2019ve made more fields readily available so your actions, like email actions, need fewer steps to request data from your TOPdesk environment.<\/p>\n
- \n
- To make your emails more personal, you might prefer to refer to someone by their first name. The First name<\/strong> field is now directly available for linked Operator and Person cards. For example, you can now add the first name of assigned persons on an Asset card via the \u2018Insert value\u2019 menu.
\n![\"Add](\"https:\/\/www.topdesk.com\/en\/wp-content\/media\/sites\/30\/first-name.png\")
<\/a><\/li>\n- The names and email addresses<\/strong> of related Branch, Location, Operator, Operator group, Person, Person group, Supplier, Budget holder, and Service window cards can now be used in Automated Actions.<\/li>\n<\/ul>\n
Get ready for NIS 2 with better logging<\/h2>\n
- The names and email addresses<\/strong> of related Branch, Location, Operator, Operator group, Person, Person group, Supplier, Budget holder, and Service window cards can now be used in Automated Actions.<\/li>\n<\/ul>\n
- An Application passwords<\/strong> section. For regular Operator cards, you still find this in My Settings. This move means that you, as the application manager, don\u2019t need to log out and log in all the time to add new application passwords to an API account.<\/li>\n<\/ul>\n
- Mid-February 2026<\/strong>: All Operator cards must be linked to a Person card. After this date, any unlinked Operator cards will get linked to an automatically generated Person card, which could lead to duplicate cards and a loss of incident history.<\/li>\n<\/ul>\n
- From 1 November 2025<\/strong>: New Operator cards must be linked to a Person card.<\/li>\n