Parent Directory
|
Revision Log
chore: add old version archive branches (2.x to 9.x-dev)
1 | # Locking Channels |
2 | |
3 | You can lock channels using `-lock` command. This sets a permission override to the target channel that denies `SEND_MESSAGES` permission for `@everyone` role. |
4 | |
5 | !!! warning |
6 | If other roles have `SEND_MESSAGES` permission allowed then members having them could bypass the channel lock. You should take care about this. |
7 | |
8 | ##### Legacy Command |
9 | ``` |
10 | -lock [ChannelID|ChannelMention] |
11 | ``` |
12 | |
13 | ##### Slash Command |
14 | ``` |
15 | /lock [Channel] |
16 | ``` |
17 | |
18 | !!! note |
19 | If the channel is not specified then the system will lock the current channel. |
20 | |
21 | #### Examples |
22 | |
23 | ``` |
24 | -lock |
25 | -lock 347382275362482 |
26 | -lock #general |
27 | ``` |
28 | |
29 | ## Unlocking Channels |
30 | |
31 | You can unlock channels back using `-unlock` command. This sets a permission override to the target channel that reverts the `SEND_MESSAGES` permission for `@everyone` role as it was before. |
32 | |
33 | ##### Legacy Command |
34 | ``` |
35 | -unlock [ChannelID|ChannelMention] |
36 | ``` |
37 | |
38 | ##### Slash Command |
39 | ``` |
40 | /unlock [Channel] |
41 | ``` |
42 | |
43 | !!! note |
44 | If the channel is not specified then the system will unlock the current channel. |
45 | |
46 | #### Examples |
47 | |
48 | ``` |
49 | -unlock |
50 | -unlock 347382275362482 |
51 | -unlock #general |
52 | ``` |
[email protected] | ViewVC Help |
Powered by ViewVC 1.1.26 |