aboutsummaryrefslogtreecommitdiffstats
path: root/docs/USERGUIDE.md
diff options
context:
space:
mode:
authorChristophe Besson <cbesson@gmail.com>2026-09-20 18:56:58 +0200
committerChristophe Besson <cbesson@gmail.com>2026-09-20 18:56:58 +0200
commit375ad7d0435a176ad593a32045a5f0182a36d505 (patch)
tree87dc2e5c5398cd2f5c5008160d259e97749b4efa /docs/USERGUIDE.md
parentbe50f1442148c21cabf039abdcae5fe20bc690e8 (diff)
downloadmeshbay-375ad7d0435a176ad593a32045a5f0182a36d505.tar.gz
fix: removing someone who never redeemed their invitation
A member row appears only when a code is consumed, so revoking someone invited to the wrong group was refused for having no row — and the node's refusal aborted the browser's removal before its hub half, leaving them a member everywhere with a live code. Revoking now cancels unredeemed codes for that group, and a node refusal no longer cancels the hub removal. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Diffstat (limited to 'docs/USERGUIDE.md')
-rw-r--r--docs/USERGUIDE.md9
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/USERGUIDE.md b/docs/USERGUIDE.md
index 9f7cea7..4d87aef 100644
--- a/docs/USERGUIDE.md
+++ b/docs/USERGUIDE.md
@@ -570,6 +570,15 @@ keeps the old one, which opens nothing written from now on.
Anything they already downloaded stays theirs. Once a file has been copied, no
software can reach back and take it away.
+Or the group's **Members** tab, from a paired browser: *Remove*. It does both
+halves — the node stops serving them, and the hub stops letting them reach it.
+
+**Somebody you invited by mistake** is removed the same way, from either, and
+it also cancels the code you sent them: until it is redeemed there is no
+membership yet, only an invitation, and taking one back has to take back the
+other. Nothing to rotate in that case — they never had the key, and neither
+the command nor the interface will tell you to.
+
If you mistype the username, `member revoke` says so rather than quietly doing
nothing.