#162 · Reconcile and verify the existing SimpleX member lifecycle
Last checked with GitLab: . Status comes from GitLab using a 2-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.
An MR completes this bounty when it is merged into main with Closes #162 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.
cp .dev.vars.example .dev.vars && pnpm dev, after rebasing on main) and fully test your change before opening the MR.
Description
Current remaining scope, reviewed 2026-10-18: Pending/queue and member approval/removal handlers already exist. Read the parity ledger and SIMPLEX_ADMIN_VERIFICATION documentation. Reconcile prior implementation MRs and award identity first, then verify the remaining native response types and linked-identity deployment evidence in an approved canary. Do not implement a second pending/gtg/remove flow or infer a global identity from a group-local contact ID.
Verification for this remaining scope
- Inventory the cited commands/schedulers on current main and link the original implementation and any recorded award before claiming new work.
- Use real local handlers/SQL/protocol paths with synthetic identities; baseline failures by name. A mock-only success or a healthy process is not live proof.
- Update both command documentation surfaces when behavior changes. Record updated / pre-release verified / released / live verified separately.
- This issue does not re-award already accepted behavior. Ask the maintainer to settle original contribution attribution before accepting a follow-up MR.
Entry point: selfhost/messaging-apps/simplex/docs/parity-roadmap-progress.md plus the current command registration and native source. Follow AGENTS.md and the bot rules.
Earlier scope (historical; current qualification above takes precedence)
Context
SimpleX has !account/!audit but no member-approval workflow.
Acceptance criteria
- [ ]
!gtg <user>(admin) approves a pending user (create/activate Authentik account, assignMAIN_GROUP_ID). - [ ]
!pending/!queue(admin) lists pending approvals. - [ ]
!remove <user>(admin) removes with--reason/--policy/--inactiveand optional--keep-sso. - [ ]
!reactivate <user>(admin) re-enables a deactivated SSO account. - [ ] User targeted by display name/contactId or linked Authentik identity (SimpleX has no @mentions or phone identity); gated by
authentikClient.isConfigured().
Technical hints
- Signal reference:
handleGtg,handlePending,handleRemove,handleReactivate; Authentik client in shared-utils. - SimpleX target: new files under
commands/admin/; admin gating viasrc/src/utils/admin-check.ts. - Link via the
linkmemapping, not a phone number. Bot'sauthentik_usernamecan lag renames; match carefully.
--- Submit a merge request that says Closes #<this issue iid> in the description. On merge to main, the GitLab webhook auto-awards feature_bounty_<tier> + the standard merge_pr (40 pts) to your scoreboard account. Your commit email must match your Authentik email. Backlog context: docs/simplex-parity-bounties.md.
<!-- bounty-reconciled:2026-10 -->
Relevant files
No relevant files linked yet.
Hints
No hints yet.
Activity
No points have been awarded for this bounty yet.
Comments
Sign in to join the discussion.
No comments yet. Be the first to weigh in.