also, I know Anita had feedback about the "Group Paywall Enabled" button specifically, which I agree with: https://github.com/Hylozoic/hylo/issues/1158

ok here are some copy suggestions: Thomas Watson Krisha Subramanian

[Payments Account] "Accept Payments for <Group Name>"

Use Paid Content to charge for membership in your group or access to a track in your group.

To start, set up Stripe Connect to accept payments for group memberships, tracks, and other offerings. Stripe handles all payment processing securely.

[Paid Offerings] "Setup Paid Content Offerings"

To charge for group membership or tracks, set up an offering. For example, if you want to create a paywall for your group, click Create Offering and set the payment terms you'd like. Options include one-time or recurring fees, price tiers, and sliding scale. Once the offering is created and your Stripe account is connected, you can check the box to enable a group paywall.

[Paid Content Access] "Manage Paid Content Access"

View who has access to paid content in your group and manage those permissions.

Thanks. Clare Politano I know wanted to write some copy! I’ll loop her in

A lot of variation/variance in how we could do this.

For example, even the concept of membership tiers is quite specific to some models of paid content but not others.

So, again, the classic challenge for us to offer something that can cater to a range of use-cases but then folks also don't have strong ideas about what their own use-case is, so they can get lost.

Maybe we need a big question mark "what do I even do" button that opens a big explainer, asking the admin to think about their use-case

"what are you trying to achieve?"... a series of questions that help them understand what they want to do and how that might map to how they can set up offerings