Mapping an existing forum group removes everyone the console did not put there, with no count or warning #333

Open
opened 2026-11-14 23:17:14 +00:00 by cgalo5758 · 0 comments
Owner

What a person cannot do today

See, before mapping a forum group to an entitlement, who is already in the group and who will be removed from it.

The mapping form asks for the entitlement and the group's name, and checks only that the group exists and is not an automatic one. At the first sync the console adds the entitled people and removes every other member, including people a forum admin added and people who have no console account. It logs the removal as drift corrected.

Unmapping does the opposite without saying so. It leaves the group's membership as it is, so whoever is in the group at that moment stays there, including anyone whose entitlement ends later.

What they should be able to do

Before a mapping is created, see how many current members of the group are not entitled, and who they are, and confirm. Before a mapping is removed, see that the group's current members stay in it.

Why it matters

A mapped group's membership belongs to the console, which is the point of mapping it. Taking over a group that people already use is the one moment where that removes people who did nothing, and the operator is not told before it happens.

Where

The Discourse operator page, group mappings. internal/integrations/discourse/web/operator.go (CreateMapping, DeleteMapping), internal/integrations/discourse/web/forms.go, and the removal in internal/integrations/discourse/workflows/activities.go.

Done when

Creating a mapping asks for confirmation that states the number of current group members who are not entitled and lists them, and no mapping is created without it. Removing a mapping asks for confirmation that states the current members stay in the group.

### What a person cannot do today See, before mapping a forum group to an entitlement, who is already in the group and who will be removed from it. The mapping form asks for the entitlement and the group's name, and checks only that the group exists and is not an automatic one. At the first sync the console adds the entitled people and removes every other member, including people a forum admin added and people who have no console account. It logs the removal as drift corrected. Unmapping does the opposite without saying so. It leaves the group's membership as it is, so whoever is in the group at that moment stays there, including anyone whose entitlement ends later. ### What they should be able to do Before a mapping is created, see how many current members of the group are not entitled, and who they are, and confirm. Before a mapping is removed, see that the group's current members stay in it. ### Why it matters A mapped group's membership belongs to the console, which is the point of mapping it. Taking over a group that people already use is the one moment where that removes people who did nothing, and the operator is not told before it happens. ### Where The Discourse operator page, group mappings. `internal/integrations/discourse/web/operator.go` (`CreateMapping`, `DeleteMapping`), `internal/integrations/discourse/web/forms.go`, and the removal in `internal/integrations/discourse/workflows/activities.go`. ### Done when Creating a mapping asks for confirmation that states the number of current group members who are not entitled and lists them, and no mapping is created without it. Removing a mapping asks for confirmation that states the current members stay in the group.
cgalo5758 added the
kind
enhancement
area/discoursearea/operator-ui
labels 2026-11-14 23:17:14 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#333