Every product that sells job posts is now configured the same way. Instead of separate fields for included posts, active jobs, and featured slots, the plan form has one control that reads back as a sentence, for example "10 one-time posts. 3 of them can be featured." or "5 jobs live at once. All of them can be featured."
Memberships
- Credits, slots, or unlimited. A membership includes a number of posts per billing period (credits, spent when the member posts and reset at the membership's anniversary), a number of jobs live at once (slots, which free up when a job closes), or unlimited posting
- Featured as a share of those posts. None, a number, or all. The unit follows the posts, so a membership can never carry two different clocks, and the form refuses more featured jobs than posts
- The employer's posting card counts the allowance down and says "featured" when the membership features that post. A full slot cap withdraws the free option without blocking the post
Job posting plans
- Bundles state their posts as credits; subscriptions state theirs as slots or unlimited. Featured is none, a number, or all of those posts. Free and one-time plans keep the featured checkbox
- Stored values and employer entitlements are unchanged, so existing plans read back as they were
Board SDK 4.20.0
board.plans.list({ purpose })accepts every purpose, includingemployer_serviceandjob_seeker_service, and plans carrypricingModeso contact-led tiers render a quote CTA instead of a price.board.plans.salesLed()is deprecated- Public company objects carry
membership(planIdand display name), andboard.companies.list({ membershipPlanId })returns one membership's roster membership_requiredis the typed error for a gated posting attempt
See memberships, create pricing plans, and the plans reference.

