본문으로 건너뛰기
모든 게시물커뮤니티

Communities: roles, invites and join links

Create a community, choose who can join, share invite links, and give the right people the Admin role. A practical guide for community owners.

MyGritWall 팀 작성읽는 데 4분

이 글은 영어로 제공돼요.

The short answer: a community is a home for a group that runs challenges together. You create it in four steps, Basics, Look, Who can join and Review, and choose whether anyone can join, anyone can ask to join, or it is invite only. You bring people in with email invitations or invite links, give one or two trusted people the Admin role, and run challenges inside it so members find each new one in the same place.

A single challenge is enough for a one-off. When a group keeps coming back, a running club, a class, a creator’s audience, a group of colleagues, a community gives it a lasting place: members, posts, announcements and a list of challenges past and present. This guide explains how to set one up in MyGritWall, what each role can do and how invitations work.

Creating a community

  1. Basics: give it a name and a short description that says who it is for.
  2. Look: pick a cover colour or picture; a live preview shows how it will appear.
  3. Who can join: choose Anyone can join, Anyone can ask to join, or Invite only.
  4. Review: check everything and create it.

The wizard suggests a few tags from the name. Tags help people find a public community. To be public, a community needs a real description and at least one tag; without them it stays a private draft, and the app shows a short checklist of what is missing. A public community is listed in Explore and search once someone besides the owner has joined.

Choosing who can join

  • Anyone can join: open, best for public groups that want to grow.
  • Anyone can ask to join: people request, and an Owner or Admin approves.
  • Invite only: people join only with an invitation.

Requests wait for an Owner or Admin, who can approve or decline each one. Approving quickly matters: someone who asked on a Monday evening and hears nothing until Friday has usually lost interest. If you cannot check daily, give the Admin role to someone who can.

Asking to join is a good middle ground for most groups. The community stays visible, but you keep an eye on who comes in. You can change the choice later as the group grows.

Owner, Admin and Member

Every community has three roles. The app explains them in a “Roles and permissions” sheet built from the same rules the server enforces, so what it says is exactly what each role can do.

  • Owner: runs the community, edits its settings, changes roles, hands it over or deletes it.
  • Admin: invites, approves and removes members, creates challenges, posts announcements and manages teams.
  • Member: takes part, posts and, in a public community, can bring a friend.

Admins can manage and moderate the community’s challenges, but only a challenge’s owner can delete it. Pick admins you would trust to welcome people and keep the posts friendly. One or two are usually enough for a group of a few hundred.

Invitations and join links

Owners and Admins bring people in from the “Invite people” dialog, by email or with invite links. An email invitation is tied to the address it was sent to. An invite link can have a label, such as “Newsletter” or “Spring class”, an expiry date and a maximum number of uses, and you can revoke it at any time. You can also ask for approval on joins that come through a link.

  • Use one labelled link per channel, so you know where people came from.
  • Give links for a single event an expiry date.
  • Revoke a link that was shared further than you meant.
  • A use only counts when someone actually gets in.

What an invitation can do is checked when it is accepted, not when it was sent. If an admin who sent a link loses the role, the link can no longer bring people into places they no longer manage. In a public community, members who are not admins can share a friend link to the community; it brings in one friend and does not pair them as buddies.

Running challenges inside it

Challenges created in a community belong to it. Members find them in one place, and when you start one, you can let everyone in the community know it is open, without adding anyone automatically. People who join a challenge in a community also join the community, if they were not members yet, and its notifications start off, so nobody is flooded.

Use the community’s Posts for the things that belong to the group rather than to one challenge: a welcome for new members, a note about what comes next, a photo from a meet-up. Keep challenge-specific posts in the challenge itself, so each stays easy to follow.

A rhythm helps: one main challenge at a time, a short break, then the next. Use seasons for challenges that run again, so last round’s members are invited back with one tap.

체크리스트

  • The name and description say who the community is for.
  • Who can join matches how open you want it to be.
  • One or two trusted people are Admins.
  • Invite links are labelled, and expire when they should.
  • A public community has a description and at least one tag.
  • Challenges run inside the community, one at a time.

A community turns a one-off challenge into a group that keeps going. Set it up with clear roles and honest invitations, then run the first challenge inside it. Start below, or see how others run theirs in Explore.

내 사람들을 위한 챌린지 시작하기

목표를 정하고, 할 일을 몇 개 추가하고, 링크 하나를 공유하세요. 무료 챌린지 참여는 계속 무료예요.

  • 크리에이터

    Seasons: the next chapter of a challenge

    Run a challenge again as a new season: same tasks and settings, new dates, and a one-tap invitation for everyone who took part last time.

    읽는 데 4분

  • 커뮤니티

    The daily roll call

    See who checked in today as a strip of faces at the top of the challenge, plus a daily group post. What shows and what never does.

    읽는 데 4분