Source
Permissions, SSO & administration — found from sitemap — Slite
Checked for Slite on 1 Nov 2026
- Page
- https://slite.com/help/revxa5CI8j1Hs4/Doc-Permissions
- Checked
- 1 Nov 2026, 09:13 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:6d48152b0a2b75f7cfc60760ddee7c3b2e7c3573083742e6dc3fce5b08e2cb44
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Cascading permissions Report an error
“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.”
-
Permission override Report an error
“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.”
-
Share menu controls Report an error
“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)”
-
Roles Report an error
“Here's a summary of the different roles you can set on docs and their associated permissions.”
-
Channel admin permissions Report an error
“change the title of the channel archive the channel restore the channel from the archive delete the channel from the archive convert the channel into a doc by moving it into another channel give others the Channel Admin role do everything writers and readers can do”
-
Writer permissions Report an error
“write move share to web share with other workspace members invite guests to collaborate set protect editing change icon archive delete do everything readers can do”
-
Reader permissions Report an error
“read comment manage doc verification see doc history see doc insights export”
-
Shared with me section Report an error
“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.”
-
Remove permission to restore inheritance Report an error
“Setting a role to No access doesn't restore inheritance. It blocks access on that doc. To go back to the parent's permissions, use Remove this permission instead.”
-
Guest access restoration Report an error
“Restoring inheritance also brings back any guests who have access to the parent.”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The Engineering Lead Permissions, SSO & administration
- The IT Administrator Permissions, SSO & administration
- The Operations Lead Permissions, SSO & administration
- The Quality Manager Permissions, SSO & administration
- The Skeptic Permissions, SSO & administration
- The Support Knowledge Manager Permissions, SSO & administration