Control who can view or edit a doc — and decide whether those settings apply to subdocs too.
How Permissions Work in Slite
By default, docs inherit permissions from their parent channel or doc.
This is called cascading permissions — it helps you manage access without having to set permissions on every single doc.
You can override these defaults at any level to give specific people access to just one doc or restrict access further down the doc tree.
Setting Doc Permissions
In the Share menu in the top right of a doc you can control:
Who can view (Reader)
Who can edit (Writer)
Whether subdocs inherit the same permissions
Who can manage the channel (doesn't apply to subdocs)
The Share menu of a channel.
Here's a summary of the different roles you can set on docs and their associated permissions.
Title
Title
Role
Permissions
Channel admin (channel-level only)
Can:
move
archive
delete
do everything writers can do
Writer
Can:
write
share to web
share with others
set protect editing
archive
do everything readers can do
Reader
Can:
read
comment
manage doc verification
see doc history
see doc insights
export
No access
Cannot interact with the doc in any way.
Inheriting vs. Overriding
Inheriting Permissions (default)
When you create a new doc under a channel or parent doc, it inherits the permissions of this channel or parent doc.
QA will get writer access for the subdocs in this channel.
You’ll see a toggle that says Include subdocs when sharing a subdoc — leaving this enabled as the default means all docs below will follow the same access.
QA will get reader access on this doc and its subdocs.
If you turn this toggle off, permissions for subdocs will be inherited from the channel instead, not the doc.
Overriding Permissions
Want to share just one doc from the channel without exposing the rest?
Open the Share menu on that specific doc and invite team members directly by typing their name and choosing a role.
The doc will appear in their Shared with me section at the bottom of the left sidebar, and they won't be able to access the parent channel or any other docs in it.
QA will not inherit any access from the parent channel.