We currently use Notion as our companies knowledge hub (it encompasses everything in the company, all our tutorials, processes, company staff, policies, resources, etc.). We are slowly migrating over to an internal knowledgebase in Front in an effort to keep things in one place (and to save money)!

I have started storing company procedures, reference sheets, and even used custom fields in “Accounts” in order to hyperlink in-depth procedures at a click for our specialized accounts.   This is serving as a great intranet resource!

We have the same scenario as @futureproof. We try to migrate post by post but it takes time because : 

• We have a lot of color in our titles and content
• Not all Markdown is copied (we struggle with tables for exemples)

One thing important for us is the way to create quick relation between pages so for some use cases we will still using Notion until new improvements in Front KB 

But overall we created really quick and most common questions are easy to find on the plugin pane for our end users. 

We’re also interested in using Front’s Knowledge Base “across our organization internally, and where it might also be useful externally.”  Unfortunately, until a knowledge base can be published securely for Intranet-only users, it’s not going to work for us.  We really need to be able to provide secure internal knowledge base access, to users who may not be using Front.   

Hi,

Our team at Front utilizes the knowledgebase to standardize processes, streamline troubleshooting, and identify automation opportunities. It also plays a crucial role in referencing past case resolutions, enabling us to resolve issues more efficiently and foster a collaborative environment for continuous improvement.

Hello, 

Our team has started utilizing the knowledge base to help external users have a single link where they can access our training materials to self-help through any issues or additional training. 

Our next step is doing the same for our internal team to organize our Support Team workflows and new employee trainings for our users to reference various common customer issues and workflows they need to solve these issues!

We plan on using one knowledge base for internal support documentation and another for external support documentation--so our colleagues can use the former and customers use the latter.