mirror of
https://github.com/status-im/status-web.git
synced 2025-02-11 20:16:37 +00:00
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>
64 lines
3.7 KiB
Markdown
64 lines
3.7 KiB
Markdown
---
|
|
id: 543
|
|
revision: '0'
|
|
language: en
|
|
title: Delegate admin functions to community members
|
|
---
|
|
|
|
:::info
|
|
Currently, you can only delegate admin functions using Status desktop. [:octicons-desktop-download-16: Download Status desktop][status-web-download].
|
|
:::
|
|
|
|
Community owners have total control over their communities, including settings, membership approvals and permissions. In addition, owners can delegate administrative functions to other community members through the [admin role][permissions-by-role-in-status-communities]. Admins play a similar role to owners, but with some important differences. Check out [Permissions by role in Status Communities][permissions-by-role-in-status-communities] for more information.
|
|
|
|
To delegate admin functions to others, owners use [token-based community permissions][set-up-your-community-permissions]. Tokens are digital assets in a blockchain (such as the [Ethereum blockchain][about-the-ethereum-blockchain]), including assets (virtual coins), collectibles and ENS names.
|
|
|
|
## What to expect
|
|
|
|
- To delegate admin functions, assign the `Become admin` community permission to a collectible or ENS name owner.
|
|
- Using ENS names to delegate admin functions is more straightforward than using collectibles, but it requires the admin to own the ENS name.
|
|
- You can create a maximum of five different `Become admin` community-level permissions, but you can apply a single permission to multiple members.
|
|
- To stop delegating admin functions, [self-destruct the admin token][self-destruct-a-token-remotely] or [delete the admin permission][delete-community-permissions].
|
|
|
|
## Choose your delegation token
|
|
|
|
You can delegate [admin functions][permissions-by-role-in-status-communities] to others using a collectible or an ENS name.
|
|
|
|
If you use a collectible, follow this process:
|
|
|
|
- [x] [Mint][mint-tokens-for-your-community] a non-transferable (soulbound) and remotely-destructible collectible.
|
|
- [x] [Airdrop the collectible][how-to-airdrop-tokens-in-status] to the person you wish to delegate admin functions to.
|
|
- [x] [Delegate the admin function](#delegate-admin-functions-using-collectibles-or-ens-names) using token-based community permissions.
|
|
|
|
Using ENS names, you don't need to mint and airdrop any token. You [delegate admin functions](#delegate-admin-functions-using-collectibles-or-ens-names) to a specific ENS name owner (such as alice.acme.eth) or a group of people under the same ENS domain (such as acme.eth).
|
|
|
|
:::info
|
|
Assets don't have the non-transferable (soulbound) and self-destructing properties collectibles have, making it harder to remove admin functions from other users. Avoid using assets to delegate admin functions.
|
|
:::
|
|
|
|
## Delegate admin functions using collectibles or ENS names
|
|
|
|
=== "Desktop"
|
|
|
|
1. From the navigation sidebar, click your community.
|
|
1. On top of the channel sidebar, click your community logo and then, click **Permissions**.
|
|
1. Click **Add permission**.
|
|
1. For the `Who holds` variable, choose your delegation option and use the table below for reference.
|
|
1. For the `Is allowed to` variable, select :desktop-admin: **Become admin**.
|
|
1. For the `In` variable, make sure your community is selected.
|
|
1. Click **Create permission**. The new permission takes effect immediately.
|
|
|
|
| Delegation option | Steps |
|
|
|:---|:---|
|
|
| Collectible | 1. Select **Collectibles**. |
|
|
|| 2. Choose the collectible and amount you want to use to delegate admin functions. |
|
|
|| 3. Alternatively, **Import existing collectible**. |
|
|
|| 4. Click **Add**. |
|
|
| ENS name | 1. Select **ENS**.
|
|
|| 2. Enter the ENS name or domain you want to delegate admin functions to. |
|
|
|| 3. Click **Add**. |
|
|
|
|
:::info
|
|
When you select the `Become admin` role, the **Hide permission** option is enabled automatically.
|
|
:::
|