* 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>
2.2 KiB
id | revision | language | title |
---|---|---|---|
305 | 0 | en | Kick or ban someone from your community |
Community owners can kick out or ban members who violate the community guidelines or behave in a toxic manner. The difference between a kick and a ban in Status Communities is that a kick is temporary, while a ban is permanent. Community owners can kick or ban members in open and token-gated communities.
In the case of minor offences or annoyances, consider kicking the offender. For major violations of the community guidelines or repeated offences, you can use the ban option. Use the ban option cautiously, as this action is irreversible.
:::info Banning or kicking a user on your Status contact list doesn't remove the contact. If you want to remove the user from your contact list, [remove the contact][remove-a-contact-from-status] or [block the user][block-someone-in-status]. :::
What to expect
- A user who has been kicked out of a community can ask to join the community again.
- A user who has been banned from a community cannot join the community again, but can request to join using a different profile.
- Users receive a notification when they are kicked out but not when they are banned.
- Users can see they have been kicked out or banned when they try to reaccess the community.
Kick or ban someone
=== "Mobile"
1. From the tab bar, tap :mobile-communities: **Communities**.
1. Tap your community.
1. From the navigation bar, tap :mobile-more-options: **More options**.
1. Tap **View members** and then, tap :mobile-more-options: **More options** next to the member you want to kick or ban.
1. Select :mobile-placeholder: **Kick** or :mobile-placeholder: **Ban**, depending on the action you wish to perform.
1. Tap **Kick** or **Ban** again to confirm your action.
=== "Desktop"
1. From the navigation sidebar, click your community.
1. At the top of the channel sidebar, click your community logo.
1. Click :mobile-placeholder: **Members** to show all the community users.
1. Hover over the user and select **Kick** or **Ban**, depending on the action you wish to perform.
1. Click **Kick** or **Ban** again to confirm your action.