Need advice on how best to treat a documentation/knowledge base that works with TalentLMS

Michael Arndt
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 8, 2019

So here's what I'm trying to accomplish and I'm looking for advice and experience sharing.

I need to create some type of knowledge base that we can use to create documentation and training material for my company. I need to create documentation that's both technical and non-technical. We're NOT a software company but a home service company in the pest control and home cleaning industry. I need to create documentation on your processes, tools, etc. that can either be referenced when needed or linked to from our LMS system (TalentLMS).

I also want to avoid, if possible, having to pay a license fee for every user when  most users only need read-only access but I do want to make sure our information is protected behind some type of login.

Confluence seems like a good first step but it doesn't seem to really be designed for my use case. Atlassian Service Desk does seem to bridge that gap but can our information be protected behind a login? The support ticket isn't something I really need right now which seems to be the core use of ServiceDesk.

Anyone ever tackled this issue themselves? I would have loved to have used something like Scroll Viewpoint but that seems to only work with Server edition and I'm on the Cloud edition.

Looking for suggestion on the best way to approach this.

 

P.S. To clarify I am getting familiar with Confluence so maybe that will do everything I need. I'm just not sure but would like to hear from anyone that has done something similar.

 

1 answer

0 votes
Alyx Jame
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 26, 2024

Creating a knowledge base for your pest control and home cleaning company sounds like a great initiative!

I understand your concerns about finding the right tool that fits your needs, especially with regards to user access and login protection. Since you're already exploring Confluence, I'll provide some insights on that and other options.

Confluence:
As you're getting familiar with Confluence, you might find that it can indeed serve your purposes. With Confluence, you can:

1. Create a knowledge base with structured content
2. Organize content using spaces, pages, and labels
3. Control user access and permissions
4. Integrate with TalentLMS using APIs or third-party plugins

However, if you find that Confluence doesn't quite fit your needs, here are some alternative options to consider:

Other Options:
1. Atlassian Service Desk: As you mentioned, Service Desk does offer a knowledge base feature, but it's primarily designed for customer-facing support. You can still use it for internal knowledge management, but it might require some customization.
2. Notion: A popular, all-in-one workspace that offers knowledge base features, including page permissions and access controls. Notion integrates well with TalentLMS using Zapier or APIs.
3. ProProfs Knowledge Base: A dedicated knowledge base software that offers features like user permissions, access controls, and integrations with LMS systems like TalentLMS.
4. Microsoft SharePoint: A robust platform that offers knowledge management features, including document management, permissions, and access controls. SharePoint integrates well with TalentLMS using APIs or third-party plugins.
Security and Login Protection:
All the options mentioned above offer some level of security and login protection. You can control user access, set permissions, and ensure that your knowledge base is protected behind a login.

Example Use Case:
Imagine creating a knowledge base article on Termite Treatment Methods. You can store this article in your chosen knowledge base platform, set permissions for specific user groups, and link to it from your TalentLMS system.

Before making a final decision, consider the following factors:

1. Ease of use and adoption
2. Integration with TalentLMS and other tools
3. Customization options
4. User access and permission controls
5. Scalability and growth potential

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events