Approving join requests and the rule book
When to approve each person who joins, how to write rules people actually read, and how to change them mid-challenge without losing anyone.
MyGritWall 팀 작성읽는 데 5분
이 글은 영어로 제공돼요.
The short answer: approve joins when the group depends on trust, such as a support group, a paid coaching circle or a small community, and leave joining open when reach matters more. Write a short rule book that says what the challenge is for, what counts, how people treat each other and what happens when someone breaks a rule. Ask everyone to accept it when they join, and ask again when you change it. In MyGritWall both are settings on the challenge, and they work together.
Most challenges never need a gate. But some groups do better when the organizer knows who is coming in, and almost every group does better when the rules are written down before the first argument. This guide covers when each tool helps, how to use it without slowing people down, and how to handle the awkward cases: a full challenge, a person you turned down, a rule that needs to change in week two.
When approving joins is worth it
Approval adds a step for every new person, so it should earn its place. It is worth it when the safety or the mood of the group depends on who is inside.
- Groups where people share personal things, such as health, money or mental wellbeing.
- Communities with a clear focus that you want to protect from spam and drive-by accounts.
- Challenges tied to a real-world group, such as a club or a class, where only members should join.
- Groups that have had trouble before and need a calmer start.
It is usually not worth it for a big public challenge whose goal is reach. Every request that waits a day is a person who may lose interest. If you turn approval on, plan to review requests at least once a day, and say on the challenge page that you do.
Reviewing requests fairly
Decide in advance what you look for, so your decisions are consistent. For most groups the honest answer is simple: approve everyone who seems to be a real person interested in the topic, and turn down obvious spam. Do not ask people to justify themselves in public, and do not turn the review into an interview.
If you turn someone down, they can usually ask again. That is good: a person who was mistaken for spam gets a second chance. If you are unsure, approve and keep an eye on how the person settles in.
Write a rule book people read
A rule book is not a contract. It is a short page that tells a newcomer what kind of place this is. If it is longer than a screen or two, few people will read it. Plain sentences beat legal language, and a friendly tone sets the mood as much as the content does.
- Start with one sentence on what the challenge is for and who it is for.
- Say what counts as a check-in, what proof is expected, if any, and how rest days work.
- Write two or three lines on how people treat each other, such as no shaming, no unsolicited advice and no selling.
- Say what happens when someone breaks a rule: a reminder first, then removal for repeated or serious cases.
- Add who to contact with questions or concerns.
- Read it aloud once. Cut every sentence that sounds like a terms of service.
Changing the rules mid-challenge
Rules sometimes need to change: a task turns out too hard, a new kind of post causes friction, or a question keeps coming up. Change them openly. Post a short note explaining what changed and why, and ask members to read the new version. Avoid changing rules in a way that takes progress away from people who followed the old ones.
Small fixes, such as a typo, can wait for a bigger update. Each change asks every member to look again, so bundle edits where you can.
How join approval and rules work in MyGritWall
The “Approve joins” setting is in the challenge form, when you create or edit a challenge. It is on by default for new public challenges and off by default for “Everyone in the organization” challenges. It is never offered for invite-only, official or paid challenges; for paid ones the form says “Paying is joining, so join approval is turned off.” People who want in press “Request to join” and see “Request sent”. They can cancel the request, and ask again after being turned down. The Owner and Admins are notified and review requests in the “Join requests” section of the Members tab, via “Review requests”, where they approve or turn down each one; the person is told. Caps and blocks still apply on approval, and if the challenge is full the request stays pending. Turning approval off later leaves pending requests waiting rather than admitting them.
The rule book is optional rich text with headings, bold, italic, lists and links, but no images or files, written by people who can edit the challenge. Every join path shows it with the checkbox “I have read and accept the rules”, and nobody can join without accepting the current version. Each save creates a new version: members see “The rules were updated” and “Accept the rules”, and keep taking part in the meantime. Managers see which version each member accepted and when. The rule book belongs to challenges; communities have “Ask to join” but no rule book. A separate setting, “Allow joining after the start”, is on by default. All of this works on the web and on the phone.
체크리스트
- Approval is on only where trust or focus depends on it.
- Requests are reviewed at least once a day.
- Decisions follow simple, consistent criteria.
- The rule book fits on a screen or two, in plain sentences.
- It says what happens when a rule is broken.
- Rule changes come with a short note on what and why.
A gate and a rule book are quiet tools. Used well, newcomers barely notice them, and the group feels safer and clearer for it. Keep approval for groups that need it, keep the rules short and human, and change them in the open. If you want to set up a challenge this way, you can start one below.
내 사람들을 위한 챌린지 시작하기
목표를 정하고, 할 일을 몇 개 추가하고, 링크 하나를 공유하세요. 무료 챌린지 참여는 계속 무료예요.