Consolidate benefits display into single card - #754
Conversation
8d07584 to
ed59dad
Compare
There was a problem hiding this comment.
This doesn't seem to handle member orgs that inherit plans from a parent, only orgs with their own direct subscriptions.
There was a problem hiding this comment.
There's still an issue here with multiple levels of benefit inheritance. Here's an org that has its own subscription plus an inherited subscription via an affiliation:
A user in this org only sees the inherited benefits from the org's direct subscription, not the org's own inherited benefits:
There was a problem hiding this comment.
There's a comment that says:
Plans the org inherits from parents/groups are intentionally excluded here -- those are an org-level concept and confuse users when surfaced on their personal page
but that's from before we were consolidating the benefits. IMO it's now more confusing NOT to include inherited benefits. In this context, users have no reason to know or care whether they have 50 requests because of their org's subscription or their org's affiliate's subscription — they should see the full total of benefits available to them.
f643585 to
6590b34
Compare
8a942a9 to
295db68
Compare
- Adds new "benefits" field to `Entitlement`, which `Plan` can compose into a single list. - Falls back to existing `Plan.benefits` value, deduplicating strings when possible. - Shows a single "As a member of Org A, Org B, you inherit: <benefits list>"
89143f5 to
4bfa43f
Compare
There was a problem hiding this comment.
There's still an issue here with multiple levels of benefit inheritance. Here's an org that has its own subscription plus an inherited subscription via an affiliation:
A user in this org only sees the inherited benefits from the org's direct subscription, not the org's own inherited benefits:
There was a problem hiding this comment.
There's a comment that says:
Plans the org inherits from parents/groups are intentionally excluded here -- those are an org-level concept and confuse users when surfaced on their personal page
but that's from before we were consolidating the benefits. IMO it's now more confusing NOT to include inherited benefits. In this context, users have no reason to know or care whether they have 50 requests because of their org's subscription or their org's affiliate's subscription — they should see the full total of benefits available to them.
|
While updating the design of the billing card, I did away with many of the action links, which all pointed to the exact same place. I found this keeps the info easier to parse and more summary-like. Billing card for a user with multiple subscriptions who is also a member of an org with multiple subscriptions: 
Billing card for an organization with multiple subscriptions and inherited benefits from an affiliation: 
|
dnass
left a comment
dnass
left a comment
There was a problem hiding this comment.
The new plan card layout and language are super clear. Looks great.
2 participants
Closes #753
Entitlement, whichPlancan compose into a single list.Plan.benefitsvalue, deduplicating strings when possible.