Restrict knowledge article templates for each knowledge base

[mcconnellsj]

Users are using the wrong template for certain knowledge bases.  It seems the templates are available for every knowledge base (going by interceptor).

A good example is the Known Error KB which should only contain articles using the Known Error template.  Conversely, we don't want the known error template used the the standard Knowledge base.

Any way to restrict this?

[Jeffery Rice]

I'm currently working on something like this for my company, however, I still have the same issue that I can still select the standard template even though it is not in the related list.  Essentially, I am trying to limit a new template that I created only to one Knowledge Base.  I am currently on Washington DC.  Any help would be appreciated.

[Tyler Herman]

Sharing something I learned in case it's helpful to other people. 

We only wanted a few of our knowledge bases to see the "Standard" template, but not see the other templates. Since you cannot select the "Standard" template from the article template related list on the knowledge base, we did something a bit iffy. For the knowledge bases we only want to see the "Standard" template, we did the following:

1. Create a new article template titled something like "IGNORE - KEEP INACTIVE" and initially make it active.
2. Associate this article template with any knowledge bases where you only want the "Standard" template to display.
3. Change the article template to inactive. Now when someone goes to create a knowledge article in one of these knowledge bases, the only template that shows is the "Standard" template.