A member cannot tell which plan their benefits come from #66

New Issue

2026-09-21T07:18:20Z

cgalo5758 commented

2026-09-21 07:18:20 +00:00

The question

The member's entitlements section lists what the organization is allowed as a flat stack, one row per rule, named by the key the rule was written against. Nothing shows which plan or which grant delivers each row: a badge reading Default appears with no context, the row naming the sources is not legible as what it is, and a member cannot see that two of the rows are part of the plan they pay for. With more than a handful of entitlements it becomes a wall. How should this be arranged so a member reads what they have and where it comes from?

What depends on the answer

The member's first page, which is where most members meet the console. The same grouping question is asked of the operator's organization page, which lists the same facts from the other side.

Options known so far

Group the entitlements under the plan or grant that confers them, so the source is the heading rather than a row.
Keep the flat list and give each row its source as a plain fact rather than a badge.

Decided when

The member pages' arrangement is decided in the same round as the operator record pages, the section groups by source, and a member reading it can say which plan each benefit comes from.

Migrated from status/issues.md at b7a0e15

## The question The member's entitlements section lists what the organization is allowed as a flat stack, one row per rule, named by the key the rule was written against. Nothing shows which plan or which grant delivers each row: a badge reading Default appears with no context, the row naming the sources is not legible as what it is, and a member cannot see that two of the rows are part of the plan they pay for. With more than a handful of entitlements it becomes a wall. How should this be arranged so a member reads what they have and where it comes from? ## What depends on the answer The member's first page, which is where most members meet the console. The same grouping question is asked of the operator's organization page, which lists the same facts from the other side. ## Options known so far - Group the entitlements under the plan or grant that confers them, so the source is the heading rather than a row. - Keep the flat list and give each row its source as a plain fact rather than a badge. ## Decided when The member pages' arrangement is decided in the same round as the operator record pages, the section groups by source, and a member reading it can say which plan each benefit comes from. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

design

area/entitlements area/member-ui labels 2026-09-21 07:18:20 +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#66