In de Module Assetmanagement kun je Assets toewijzen aan een Person, Dit kan allen op basis van de samengestelde naam.
In onze organisatie (wij werken in 1 TOPdesk omgeving met 7 gemeenten en onze eigen organisatie) komen diverse personen met dezelfde naam voor en zijn er personen die voor meerdere organisaties werken. Het vinden van de juiste persoon is dus vaak ‘lastig’ waardoor er verkeerde koppelingen ontstaan. Ook het importeren van uitgegeven Assets op basis van Excel lijsten gaat hierdoor niet goed.

Mijn verzoek./ voorstel is om de toewijzing niet te doen obv de samengestelde naam maar ob het 9alrijd unieke) e-mailadres of de TOPdesk- login naam (bij os UPN).

Zijn er meer collega's die hier tegenaan lopen?

Ik heb hiervoor zojuist een RFC ingediend op tip.topdesk.com:


 

Enable Linking Assets to Persons/Operators Using Email Address

User Story

As a TOPdesk user responsible for Asset Management, I want the ability to link an Asset to a Person or Operator based on their unique business email address, so that I can reliably select the correct individual even when names are not unique, because many medium and large organizations have multiple employees with identical or similar names, which leads to incorrect asset assignments and data quality issues.

Current Situation

In the Asset Management module, Assets can be linked to a Person or Operator. However, the search and selection mechanism only allows filtering based on the composed name (first name + last name).

In organizations with thousands of employees, this is often not unique. As a result:

• Assets are sometimes linked to the wrong person.

• Bulk imports or automated integrations become error‑prone.

• Manual corrections consume unnecessary time and effort.

The email address, on the other hand, is always unique and already stored in TOPdesk for both Persons and Operators.

Requested Change

Introduce the ability to search, filter, and link Persons and Operators in the Asset Management module using their email address in addition to the composed name.

This could be implemented as:

• An additional search field for email address

• Or extending the existing search to include email address as a searchable attribute

• Or showing the email address in the selection list to help users distinguish between individuals with identical names

Benefits

• Improved data accuracy: Assets are linked to the correct person.

• Reduced administrative errors: Especially during imports or bulk updates.

• Better usability: Users can quickly identify the correct individual.

• Scalability: Essential for large organizations with many employees.