How to Set Up Your Workspace

Having your workspace tailored to your needs from the start eases adoption and maintenance. In this article we have outlined some high-level strategies for you.

For more practical information, head over to  Workspace Setup .
Table of contents


Channels

Channels let you organize your knowledge into meaningful categories and help you manage who has access to the information.

When you set up your different channels the first thing to do is to map out the content that you would like to include in your knowledge base and then the (groups of) people that need access to that content.

The overlap between audience and content forms the blueprint for setting up your channels. You can read more about this and the different approaches for setting up your How to Structure Your Slite Account .
Just remember, keep it simple!
Setting up channels will not only help with organizing the content but also help you maintain the information. We recommend appointing at least one admin per channel who is responsible for the upkeep of their channel.

Permissions

Slite is designed for collaboration. We recommend keeping channels public (internally) and encouraging people to actively contribute to the knowledge base as much as possible.

Of course, not all information should be editable or accessible to all users, and this is where our cascading permissions come in.

You have 4 different options that you can combine to cover all different needs:

Public channel
When "Everyone at company_name" is not set to 'No access', everyone will have access to the channel internally.

Public channel with selected editors
Notice how John and Iria have been made writers, while everyone else can only read the channel.

Public channel with hidden docs
When you associate permissions to a channel, they will be applied to its subdocs. If you need, you can alter the automatically set permissions based on your needs.

In this case, everyone is a reader in the "Getting started with Slite" channel. However, only John, Iria, and Anouk will have access to the current subdoc.

Private channel
Much like the example above, channels can be made private. Just set "Everyone at..." to "No access."
Bonus tip: to make managing the permissions easier, you can set up  User Groups , and manage access in bulk.

Again, think about the groups of people that need similar access when setting up user groups, and keep it simple. Try not to add people to multiple user groups.

Content

When adding content to your channels we recommend using a similar structure for each channel. This makes it easier to navigate the content in your account, gives people clarity on what they should document, and is more visually pleasing.

Each team could for example have its handbook, OKRs, and a place to document their meetings:
Use templates for the different sections you would like teams to include in their channels.

More information on how to create templates can be found in  Templates .

Furthermore, we recommend creating a landing page for each channel. One that explains what can be found in this channel and has an overview of the most important docs.

You can leverage our AI feature Generate a directory to automatically build this for you. Of course, you can always tweak it and add some personal flavour to the page, but this helps you to beat the blank canvas syndrome.