Meet the new Knowledge Base Explorer

Dank voor de update van het kennissysteem en ik heb hier gelijk een vraag over.  Wij zitten te springen om de mogelijkheid kennisitems in te delen per behandelaarsgroep. (rechten)

Kom in het filmpje van het vernieuwde kennissysteem onderstaande tegen, betekent dit dat je nu kan  filteren op behandelaars per vestiging?

En nog niet kan uitsplitsen in behandelaarsgroep? Bij ons staan alle behandelaars op 1 vestging. En gaat dat nog wel komen?

In welke versie kunnen we deze update verwachten?

Sta te springen om de migratie te testen in de test omgeving😎

​@Stefan van Opstal can you help with answering? 

Where do we find the KB migration guide?

super jammer, dat wederom dit nieuws niet vertaald kan worden naar het Nederlands

Hoi ​@Anneke Ligthart  je bent echt net iets te vroeg, ik was druk bezig met een verbeter implementatie in de Community, namelijk de vertaal optie en zie staat sinds nu net aan. 

Vanaf nu kan je alle content in de Community, en dus ook de product updates vertalen via de vertaalknop bovenaan:

 

very very excited as today is also the day we make the step to the new SSP. Thanks TOPdesk for another nice and cool improvement!

Dank voor de update van het kennissysteem en ik heb hier gelijk een vraag over.  Wij zitten te springen om de mogelijkheid kennisitems in te delen per behandelaarsgroep. (rechten)

Kom in het filmpje van het vernieuwde kennissysteem onderstaande tegen, betekent dit dat je nu kan  filteren op behandelaars per vestiging?

En nog niet kan uitsplitsen in behandelaarsgroep? Bij ons staan alle behandelaars op 1 vestging. En gaat dat nog wel komen?

 

 

Hi Cees,

This of course is still the million dollar question. Unfortunately there isn't an easy answer to this. Let's start with the good news. This is still part of our vision and roadmap for the future. Now the bad news, we started by building and testing a prototype for operator filters based on a new concept for the future of the whole TOPdesk platform: Access groups (a combination of folders, linked operator groups and permissions.

While testing we quickly realized this solution was not scalable to other modules and therefor we are back at the drawing table phase. We want to take our time (and yes we already have been taking our time) to give you a secure\proper solution that is scalable and future proof.  

Hi Sanne,

always glad to hear people are excited to test this out! The exact version is being picked by our release team and this is something that we hope to have available for you before the end of this week. Will update this post as soon as I know the version!

The migration wizard guide can be found on our documentation portal: https://docs.topdesk.com/en/migrating-to-the-new-explorer.html

And in the tool itself once the release has gone through our release pipeline. We expect it to become available in your environment in the next two weeks. 

Some questions that came to mind after watching the preview video:

1. Can you create subfolders within folders?

2. The video shows a "Knowledge manager" at the folder level:
   - what can this be used for?
   - can Knowledge managers be set on Knowledge Items, or only the folder in which they reside?
   - it only shows individuals listed in the Knowledge manager drop down in the video, can teams of people be set as the Knowledge manager? (eg Operator groups/Person groups

3. The Availability tab only shows options for Self-service portal access (Visible/Not visible/Visible for a certain period) - will there still be an option for making knowledge content available publicly/externally? (Though I note this was the Availability tab for the folder, rather than a KI, so perhaps its still an option on the KI Availability tab?)

4. Are there any changes to the KI template? Most importantly are there still sections for “Comments for Operators” and “Keywords”?

5. Can different areas of the Knowledge Base (folders/knowledge items) be permissioned granularly - eg only available to assigned operator groups/permission groups?

Many thanks!

EDIT: Found an answer to question 1 about subfolders from the slides in your What’s New @ TOPdesk – July 2026 webinar:

​@Stefan van Opstal  another question for you 😉

I learnt today in the What’s New @ TOPdesk-webinar that knowledge managers (for the folders) will be an operator account. This seems like a bad idea! Currently the “Manager” (which I feel should be called “Owner” rather than “Manager”) for each KI are operator groups rather than individual operators. We do of course not want to assign management/ownership of knowlegde base objects to a single individual who may change role, quit their job, etc.

​@Glenn, here are the answers to your questions

1. Can you create subfolders within folders?

   • You found this already, but yes you can make subfolders. There is no limit to how deep you can go, but of course our advice is not to go too deep.

2. The video shows a "Knowledge manager" at the folder level:
   - what can this be used for?
   - can Knowledge managers be set on Knowledge Items, or only the folder in which they reside?
   - it only shows individuals listed in the Knowledge manager drop down in the video, can teams of people be set as the Knowledge manager? (eg Operator groups/Person groups

   • ​​​​​​​​​​​​​​​​​​​​​​​​​​​​The manager field has the same purpose as it has on a KI. You can still set the both.

   • It is used to show who owns this part of the knowledge base. Currently it is just an indicator. In the future we want to make sure you can link actions to this field. 

   • With regards to who can be selected, this is both operators and operator groups. Persons and person groups are excluded. KI's will get an author and an owner field in the near future. ​@Magne B. hope this answers your question.

3. The Availability tab only shows options for Self-service portal access (Visible/Not visible/Visible for a certain period) - will there still be an option for making knowledge content available publicly/externally? (Though I note this was the Availability tab for the folder, rather than a KI, so perhaps its still an option on the KI Availability tab?)​​​​​​​​​​​​​​

   • Indeed the shown settings are for folders. The availability controls for KI's is still the same. We currently do not have a external navigation/portal for folders and KI's (something that we envision for the future), so for now those settings can only be set for individual KI's.

4. Are there any changes to the KI template? Most importantly are there still sections for “Comments for Operators” and “Keywords”?

   • ​​​​​​​No the setup of a KI is still the same. For folders we chose to only have an description field, as they don't interact with for instance incident cards. 

5. Can different areas of the Knowledge Base (folders/knowledge items) be permissioned granularly - eg only available to assigned operator groups/permission groups?

   • ​​​​​​​Currently not. We do want to support this in the future. We have build and tested a prototype based on a new permission and filtering system. Although filtering the knowledge base was partially successful, it turned out that is wasn't scalable for the rest of our product. A team is currently researching how this can be made in a way that it is scalable, secure and future proof. 

We have the same issue where knowledge owners/managers leave (or change post).
There is no tool to migrate knowledge ownership/management from person A to person B and all anonymised operators all look the same e.g. *************** so it's too late at that point as other knowledge managers who have left share the same name **************** 

equally, knowledge owner/manager x under post y changes roles within the org. It would be nice for a tool to say knowledge owner/manager X with post Y knowledge is now owned by knowledge owner/manager Z

The version for this release is 16.07.004. You can therefor expect the migration banner for the new explorer to show up somewhere between tomorrow and the first few days of next week. 

In terms of the migration, with the existing structure we have for Knowledge Items, will it just convert that into the new format or structure or will it disrupt the way we have it arranged at the moment?

For example, we have a top level KI or ‘parent KI’ called Office 365 and Collaboration. We then have KIs nested underneath this on MS Word, Teams, Zoom etc

We also have some KIs here that are operator only and some that are available to all users

Once the switchover takes place, does it maintain this existing structure and also availability, or will any of that change?

Since folders are the new parent item, during the migration the once toplevel KI will be duplicated into a toplevel folder. The original KI will be moved under that folder preserving all information and connected links. The description of the original KI will be used for the description of the folder. Visibility filters will stay in tact and will work the same way as before (of course until in a later time we have introduced filtering for operators, persons and groups of both of them.

It's advised to do the migration first on your test environment to see how long the migration takes and what the result is.

Hope this answers your question. 

Vanochtend zag ik dat in onze testomgeving de migratieopties voor de nieuwe kennisbank verkenner beschikbaar waren. Ik heb de migratie direct uitgevoerd.

Van de ongeveer 520 kennisitems waren er slechts twee waarbij een probleem werd geconstateerd. Nadat deze waren opgelost, kon de migratie worden gestart.

Na de herstart van de testomgeving begon het migratieproces. Mijn geduld wordt echter behoorlijk op de proef gesteld, want na twee uur staat de voortgang nog steeds op 0% gemigreerd... 😅

​@Egidio We are looking into it. During the beta test we have seen cases where it took longer, but just to be sure we will dive into your case. Will update this reply when I know more. 

-- UPDATE --

Something indeed is going wrong. Not so much due to the migration but in a database configuration of public knowledge articles that, probably during a reseed, got mixed up. Our SaaS support is now looking into it. After they have fixed it the migration should continue. 

Rest assured that for your production environment this issue will not happen. 

dat was ook mijn gedachte! maar wanneer ik de migratie zou inplannen dan kan ik niet kiezen voor de testomgeving.

@TOPdesk: graag jullie reactie!

​@Stefan van Opstal zie de vraag van ​@dekoen kan jij hier iets over zeggen? 

Dan ben je al een stap verder… Ik heb een aantal KI's met een ‘algemene foutmelding’ maar zie niet wat er fout aan is 😅

Hallo ​@dekoen & ​@Sanne Haller

Het antwoord voor jullie beide is om hiervoor een ticket aan te maken bij onze support afdeling.

​@dekoen vreemd dat je in het formulier niet jullie testomgeving kan kiezen. Die zou je namelijk wel gewoon moeten kunnen zien in de drop down.

​@Sanne Haller als je hier kennisitems ziet is het advies deze eens te openen en een kleine wijziging te maken in de tekst en deze dan op te slaan. Dit wil het probleem wel eens verhelpen. Tenzij het er honderden zijn, dan helpt support je graag verder om de synchronisatie te resetten.  

Looking forward to implementing this new update.

Will the links/paths to existing knowledge items change after migration? Just thinking about any links we have (e.g. public KIs) posted outside of TOPdesk.