Once a group grows large, management shifts from "chatting" to "operations." In Potato, group owners and administrators actually have quite a few capabilities, but many people only use mute and kick. This practical checklist is suitable for administrators who have just taken over a small group of a few dozen people or are managing a community of several hundred.
First, distinguish roles: group owner, administrator, regular member
Potato groups usually have three role levels. The group owner has the highest permissions and can add or remove administrators, change the group name and avatar, and adjust the group type; administrators perform daily management according to the permissions granted to them; regular members can only send messages and participate in interactions.
It is recommended that the group owner not hand all permissions to the same administrator at once. For example, members responsible for bringing people in only need the "invite" and "view members" permissions, while members responsible for content review should separately be given "delete messages" and "restrict speaking." The finer the permissions, the easier it is to pinpoint problems when they occur.
The group owner account itself should also be protected. If the group owner account is lost, group management will become passive. For issues such as abnormal login, not receiving verification codes, and device switching, you can refer to the account troubleshooting steps in the Potato FAQ.
How to configure permissions: a setup checklist you can follow directly
After entering group settings, check the following toggles one by one; this covers most daily scenarios:
- Send messages: For new groups, it is recommended to enable this first, observe for a few days, and then decide whether to tighten it.
- Send media and files: If the group has a lot of image spam, you can allow only administrators to send them.
- Add members: Give this only to core administrators to avoid runaway member growth after links are casually forwarded.
- Pin messages: Give this to the content operations role to make it easier to publish group rules and event notices.
- Delete messages: Keep at least two administrators with this permission to prevent no one handling issues when one person is offline.
- Ban members: Grant this cautiously, and it is best to sync the reason in the administrators' small group before acting.
If the group also serves an announcement function, you can pair it with the channel usage mentioned in Potato news and feature updates, separating "read-only notices" from "free discussion" to reduce the workload of administrators repeatedly clearing the screen.
Invitations and join review: controlling the entrance is easier than cleaning up afterward
There are two main invitation methods: adding members directly, and sharing invite links or QR codes. For groups with more than 100 people, it is recommended to use link invitations and change them regularly. Once a link is posted on a public platform, it may be forwarded in bulk, and at that point kicking people alone is unlikely to stop it.
After enabling join review, new members need administrator confirmation before entering. During review, you can look at the person's nickname, avatar, and application time, and directly reject accounts that are obviously advertising accounts. A common scenario: a study group received more than 60 join requests within two days, about half of which had random-character nicknames and empty avatars. After the administrator enabled review and set "applicants must answer a question," spam applications decreased noticeably.
If the group needs automatic welcome replies, keyword reminders, or join verification, you can learn about Potato bot usage instructions and hand repetitive work to automation tools, but do not give bots excessively high management permissions.
Daily review: slow mode, mute, and handling violations
When group messages come too fast, slow mode is the most direct tool. Setting the interval to 30 seconds is usually enough to bring discussion back to a readable state; during events, you can temporarily lower it to 10 seconds and restore it afterward.
When handling violations, it is recommended to follow the order of "remind first, then restrict, then remove," and pin a short set of group rules in the group. Take screenshots before deleting messages, and explain the reason in the administrators' group when banning members to avoid accidental penalties and disputes. For accounts that repeatedly post ads, banning directly is more effective than repeated muting.
Collaboration among administrators is also worth agreeing on: who handles morning review, who handles the evening peak, and who makes the final call in disputes. Writing these into the group announcement is more reliable than calling people ad hoc in the group. When handling member data, you can refer to the Potato privacy notice and collect only the information necessary for management.
Common issues and next steps
If you encounter an invite link that will not open, administrator permissions that do not take effect, or a member list that is out of sync, first confirm whether the app is a relatively new version, then try leaving the group page and entering again; if there is still no improvement, record the time and operation steps to make troubleshooting easier. If you need to install or update the client, you can go to the Potato download page to get the corresponding version.
There is no once-and-for-all setup for group management; it is more about continuous fine-tuning as the number of members and topics change. First sort out roles and permissions, then handle invitations and review, and finally use slow mode and group rules to maintain order. Most groups can then run stably.
Continue reading: downloads and installation, accounts and verification codes, groups, channels, and bots, and privacy and security.
