b88f7e73da
* setup md/mdx * add test page * setup mdx provider * Add breadcrumbs * links -> routes * add information box * add more remark plugins * text InformationBox * setup contentlayer * add testing docs folder * setup docs static generation * add ssg to blog too * add Shortcut component * add SearchButton * add hook for keyboard shortcuts * update main docs page * update main learn page content * side-bar -> sidebar-menu * rename docs pages * add heading anchors, use new components * add table of contents to docs * move styling to breadcrumbs * cleanup markdown examples * change slugify fn * update getting-started.md * add highlight matches component * update learn pages * rename website InformationBox to Admonition * ?enable user-select * add static helpers to epics * simplify components structure * update insights layout * add link tree utils * add search engine * update docs import * update contenlayer * add docs indexer * support code block highlighting * search index * fix types * remove supporting files * update tree builder * make build work * update docs * update label * update toc * add config.json * update menu * search index import * learn -> help * fix md file * update toc * fix code snippets * add help index route * remove testing files * add original docs * migrate getting started * migrate messaging-and-web3-browser docs * migrate network-nodes-and-statistics docs * handle empty content * add navigation config * wip * migrate status-wallet docs * migrate to new admonitions format * migrate your-profile-and-preferences docs * migrate part of status-communities docs * mv * rm log * index * fix lint * fix warn * fix title * fix docs layout * udpate next.config * use lowercase lang * generate contentlayer types before typechecking * update docs images * update help routes --------- Co-authored-by: Felicio Mununga <felicio@users.noreply.github.com>
3.0 KiB
| id | revision | language | title |
|---|---|---|---|
| 662 | 0 | en | About view-only channels |
:::info Currently, you can only set up and manage view-only channels using Status desktop. [:octicons-desktop-download-16: Download Status desktop][status-web-download]. :::
[Channels][channels-your-quick-start-guide] are spaces for conversation, discussion and information sharing. By default, all community members with access to a channel can read and send messages.
As a community [owner or admin][permissions-by-role-in-status-communities], you can set a channel as view-only. To learn how to do that, check out [Set up a view-only channel][set-up-a-view-only-channel].
A read-only channel helps maintain clear, uninterrupted communication for specific purposes. While members can't respond directly in these channels, they are crucial in keeping your community informed and engaged.
View-only channel permission
When you [set up a channel permission][set-up-channel-permissions], only members who meet the criteria for that permission can perform the associated action within that channel.
This is how the View and View and post channel permissions work in your community.
| Channel permission \ Member | Members not meeting the criteria | Members meeting the criteria | Owner and admins |
|---|---|---|---|
| None | :material-check-all: | :material-check-all: | :material-check-all: |
View |
:octicons-x-24: | :material-check: | :material-check-all: |
View and post |
:octicons-x-24: | :material-check-all: | :material-check-all: |
(:material-check-all: view and post, :material-check: view only, :octicons-x-24: no access)
:::tip Members with view-only access to the channel can still [react][react-and-reply-to-messages] to messages in the channel with emojis. :::
Using a view-only channel
View-only channels can help keep your community organized and focused. Here are some ideas on how you can use view-only channels.
-
Community announcements and updates
To keep important announcements or updates clutter-free, use a view-only channel. Only community owners and admins can write in these channels, ensuring your message is delivered without distractions.
-
Information sharing
If there are specific resources or guidelines that members need to access regularly, a view-only channel is as a convenient and easy-to-find repository. For example, you can share information that new community members may find helpful.
-
Learning communities
In learning communities, view-only channels allow owners to share exercises and training materials while keeping the conversation focused.
-
Voting or pooling areas
Because members with view-only access can still [react][react-and-reply-to-messages] to messages in view-only channels, owners can use them for voting on different topics or proposals.