Five roles, and none of them is everything.

Handing someone the keys because they need to delete one message is how group chats fall apart. The roles here are separate on purpose.

Staff seats and codes The class door

The five.

Owner — Created it. Cannot be demoted by anyone else's action.
Admin — Runs the community: approves requests, manages staff, opens rooms.
Staff — Holds a named seat — a teacher, a manager, a coordinator — and admins the room that seat belongs to.
Moderator — Can flag and act on what is posted without holding the rest of the keys.
Member — Is in the room.

Staff seats and their codes.

A seat is a name and a title, written when the community is created or added later. Each one carries an eight-character code, visible only to an admin, which the person named on the seat uses to claim it.

The alphabet the codes are drawn from has no I, no L, no O and no U, so nothing in a code can be read as something else when it is written on a staff-room whiteboard or read down a phone.

One use — A claimed code stops working.
Admin-only — Codes are never shown to members, and never returned in search.
Re-issuable — Lost one? An admin regenerates it and the old one dies.
Rate-limited — Guessing at codes is capped, per person, per hour.

Approving someone straight into a role.

Somebody asking to join a private community can say what they are asking as — a parent, a teacher, a supplier. The admin sees the title with the request and can approve them into that role in one action, instead of letting them in and then hunting for them in a member list to promote.

Start your community.

A name, a picture, and the people in it. Classes, staff seats and the verified tick are there when you need them. All of it free.