How to Create an Internal Wiki in ClickUp

An internal wiki/knowledgebase provides a central location for new and experienced employees to read and understand more about your company history, values, goals, expectations, and how you do things.
But the million dollar question always becomes: How do you create an internal wiki and where should it live?
Yes, there are a ton of different solutions out there, but building it inside of ClickUp, keeps it in one system and helps keep it close to your work.
A lot of teams start by building all of this in Google Docs. Which is fine, but it's a recipe for "where can I find that document?" and just a bunch of documents that collect dust and cobwebs.
As we always say at ZenPilot, "The process needs to live where the work get's done". If I build my internal wiki/knowledgebase with my SOPs and other documents (inside of ClickUp), I can relate these directly to the tasks that need it.
Here's how to build this inside of ClickUp:
0:00 - Introduction
1:12 - Where to Create Your Knowledgebase
2:28 - Tips to Make Your Knowledgebase More Visible
3:58 - The Knowledgebase Structure
6:26 - Documentation Templates
8:11 - What's Included in Your Knowledgebase?
11:29 - Permission Settings
12:57 - The Process For Building Documents in Your Knowledgebase
14:31 - Connecting Your SOPs to ClickUp Tasks
16:58 - A Process For Updating Your Documents
18:30 - Conclusion
🎥 Video - How to Use ClickUp Docs (A Step-by-Step Tutorial): • How to Use ClickUp Doc...
📖 Read the guide: www.zenpilot.com/blog/how-to-...
--------------------------------
As ClickUp's first and highest-rated solutions partner, we've helped over 2,700 agencies streamline their operations in ClickUp.
📈 Interested in learning how we've helped thousands of agencies double productivity, maximize profits and improve client retention? Check out our proven process: www.zenpilot.com/agency-produ...
📞 If you're ready to experience the power of world-class operations, schedule your free agency ops strategy call here: www.zenpilot.com/call?...
--------------------------------
📚FREE AGENCY RESOURCES 📚
👥 Join the FREE ClickUp for Agencies Community: / 12842198
⚡️ Want to see how your agency operations stack up against 2,000 other firms? take the 20-question benchmark: tools.zenpilot.com/pm-benchma...
📕 Download the 47-page guide on how to implement ClickUp for agencies: www.zenpilot.com/how-to-imple...
📨 Get biweekly agency ops insights from our newsletter: www.zenpilot.com/first-class-...
🎁 FREE client onboarding ClickUp template for agencies: www.zenpilot.com/client-onboa...
--------------------------------
⚠ Disclaimer: The videos on our KZbin channel are for informational purposes only and are not intended as an endorsement for any of the products or services that we feature.
#clickup #clickuptutorial #agencylife #projectmanagement

[@exposedhobo]

It appears that the permission settings section is inaccurate. According to my understanding, it is not possible to restrict member permissions at the page level. I have learned that there is a planned fix for this issue sitting in the ClickUp planned Canary for 2 years now. Therefore, I'm not sure how you were able to mention this feature in your video.

[@markhoffman3379]

Trying to understand when to keep info in a wiki vs a task description. For example, I have a list in clickup that is my web design task list. This has a ton of tasks and subtasks with specific tasks ranging from Email client this update to how to update the DNS records. Do you keep that info in the task description or the wiki? Where is the line drawn to determine when to use one vs the other? How to prevent overlap info which could conflict down the road if not found?

[@ZenPilot]

The big push for putting it all in documents and linking to tasks is that it makes it much easier to manage and update. If you build templates and then deploy that template 50 times for active work, it's hard to update those tasks in the wild if they have their own description and aren't linked to a central SOP. I prefer a mix of both. You can add some description to the description, but the instructions (at least for larger things) should be in a central SOP and you can use that block link feature to call out a specific step within your SOP.

[@AdamLundquist]

Where would you put templates for deliverables? As an example if you had an initial audit template

[@ZenPilot]

You can put the SOP for this in the Delivery section of your wiki. But you'd build the workflow in a process library. You can learn more about this here (kzbin.info/www/bejne/iZXJZaubed2Igbcsi=Lomiv4UggUpggr6J).

[@1stDigitalAgency]

Jeff, The title of the video is "How to..." however, there is no time where you actually show us how to. It's you showing us what's in yours. It's like a long advert on how yours looks. Most of your videos are like that, you don't actually show how things are done. I know you are selling your services but there's no harm in just showing us how things are done. The worst thing is to watch a 30-minute video that does not do what the title said it would do. There is nowhere in the video where you show us step-by-step how to create? If your videos are for experts then state in your video that its for experts.