Bugs
Complete

Org page Members list is missing per-member action menu (inconsistent with group page)

## Bug The **Members** section on the organization public/dashboard page has no per-member action menu — there is no `...` button on each row. To change a role, remove a member, or access any management action, the Owner has to navigate away to the dedicated **Manage Members** page. This is **inconsistent with the group page**, where the Members list has per-row `...` menus offering *Change to Co-Organizer*, *Remove*, etc. inline. See screenshot: the Members card on the org page lists each member (Christopher, alexis, Rita, test, Yuri, Drew, Taylor…) with role + joined date, but no action menu on the right. ## Expected Make the two surfaces consistent. Two acceptable approaches: ### Option A — add the inline `...` menu on the org page (my preference) Matches the group page pattern. Owners can change roles / remove directly from the inline list. Low friction, fewer clicks, and the page already has enough horizontal room. ### Option B — remove the inline `...` menu from the group page If the product direction is to keep member management strictly inside the Manage Members page, then the group page should match — strip the inline actions and add a prominent **Manage members** button instead. Either way, pick one pattern and apply it to both surfaces. ## Reproduction 1. Open any organization's public/dashboard page as its Owner. 2. Scroll to the **Members** card. 3. Observe: no `...` menu on any row; only a `View all 30 members` link at the bottom. 4. Compare against the equivalent group page — `...` menus present on each row. ## Related - **Fider #75** — Manage Members page has no breadcrumb; if we adopt Option B (force users into Manage Members), that bug becomes even more important to land. - **Fider #76** — Group member management menu missing an Organizer promotion option. If Option A is chosen here, the same action-menu pattern carries the same gap on org — worth auditing both menus together. - **Fider #71** — `LAST_OWNER` guard blocks promotion to Owner. Whichever surface ends up owning role changes, it will run into this. ## Found by Manual testing

0 Comments

Sign in to comment

No comments yet. Be the first to share your thoughts!