Integrate Slack with Wiki for Knowledge Management
Slack is being used by an increasing number of companies as an internal social networking service. However, many companies are simply using it as a chat tool. If Slack could be used like an internal wiki tool, it would enable more efficient information sharing.
In this article, we will explain in detail how to use Slack as an internal wiki and how Slack and internal wiki can work together.
This article will contain:
· How to Use Slack as an Internal Wiki
· Disadvantage of Using Slack Only
· Slack Wiki Integration
· GROWI.cloud, an internal wiki tool with Slack integration
How to Use Slack as an Internal Wiki
The Slack application itself does not include an internal wiki feature, but it is possible to use existing functionality to do something similar. Here are two ways to do so.
Using the post function
- First, create a dedicated channel in your workspace to use as an internal wiki.
2. Once in the channel, click the + button in the lower left corner and select Create Post.
3. Write text on the post screen
4. Share the post on your channel
Use the bookmark function
- Move the cursor over the message to display the menu and press the bookmark button.
2. Click “Later” on the sidebar on the left side of the screen to see a list of messages you have bookmarked and saved.
Disadvantage of Using Slack Only
We have shown how Slack can be used like an internal wiki, but because Slack is designed solely as a chat tool, it is not well suited for storing internal knowledge. So what exactly are the disadvantages?
Old information is swept away
Due to the nature of chat tools, information is constantly being exchanged one after another, and even if important knowledge is passed along, it is quickly swept away by new information.
In a channel with active communication, dozens of exchanges may occur in a day. If this happens every day, important knowledge will be overlooked no matter how careful you are.
Difficult to find the information you want
Slack has a search function, but finding the information you are looking for is often difficult. This is because Slack does not have a hierarchical structure of documents, but rather just a history of chats.
The best way to search is to look for keywords you may have been typing when you sent the chat, but you may have trouble remembering those keywords. Or, you may not be able to find the document you are looking for due to the large number of other documents found in your search.
The free plan does not allow you to see posts older than 90 days
With a paid plan, this is something you don’t have to worry about. However, with a free plan, you can’t see posts older than 90 days.
For example, you can’t say, “Oh, there was a thread about 6 months ago where you were talking about something important about Project A. What did we talk about?”
If you are aiming for more secure knowledge management, it is recommended to move to a paid plan.
Slack Wiki Integration
As mentioned earlier, using Slack alone is unsuitable for knowledge management. The tool we would like to incorporate is the internal wiki. Although the internal wiki does not have a chat function, it is an effective tool for knowledge management.
In this section, we will explain the advantages of integrating Slack with an internal wiki.
Easily disseminated internally
By integrating the internal wiki with the Slack chat tool, you can set up notifications to be sent to specific channels when pages are created or updated.
With just the above settings, you can easily inform people within your company.
Once information was shared to a channel in Slack, it was not possible to review it without going back to the past. With the internal wiki, information can be easily accessed, making it easier to disseminate information and manage information and knowledge in the workplace.
Reduces the chance of missing information and confirmation
By integrating the internal wiki with Slack, it is easy to set up notifications to be sent to specific channels, making it difficult for information to be omitted.
In addition, since Slack is being used, it is less likely that information will not be checked, and information can be shared smoothly.
Less likely to fail to update information
The following are some of how you can use Slack in conjunction with the internal wiki:
- Create a channel in Slack for notifications of page-by-page updates
- Set up notifications to be sent to the above channels when page updates are made on the internal wiki
- Make an update
- Notification is sent to the channel
In this way, you can check at a glance when a page that needs updating has been updated, and when, on the contrary, it has not been updated.
Especially, since procedure manuals need to be kept up-to-date and correct at all times, the above settings can be used to properly manage them.
GROWI.cloud, an internal wiki tool with Slack integration
Finally, I would like to introduce GROWI.cloud, our internal wiki service that allows Slack integration.
GROWI.cloud
GROWI.cloud supports Markdown and provides powerful functions for you to manage documents and files. It also boasts high security and various authentication methods are available to simplify authentication management, including LDAP/OAuth/SAML.
Other than organizational use, GROWI.cloud is also available for individual use and you can always start with a free trial here. After the one-month free trial, you can change your plan into either the individual, duo, or trio plan, OR continue to use the personal plan for FREE with a maximum of 25 users! Go to price & features to learn about the details.
GROWI.cloud origins in Japan and is now also offered in the Philippine and other countries which allows customers to use the service in English.
Go to GROWI.cloud to know more about us. You can also follow our Facebook to see updates about our service.
