Per-block content gating lets you restrict specific sections of a post rather than the whole article. A reader without access simply doesn’t get that section — it is removed from the page, with no gate or placeholder in its place — while the rest of the post reads normally. This is useful for premium analysis, data tables, extended Q&As, or any content you want to reserve for subscribers or donors.

How to set it up

Per-block gating works on Group, Stack, and Row blocks. To gate a section:

  1. In the post editor, wrap the content you want to gate in a Group block (or Stack/Row).
  2. Select the Group block and open the Block tab in the right sidebar.
  3. Open the Access Control panel and choose an Access mode:
    • Gate — pick one or more of your existing content gates under Gates. The block follows whoever those gates let through.
    • Custom — set rules on the block itself, without involving a gate. You can require readers to be logged in, to have verified their account, or to meet a paid condition such as an active subscription or institutional access.
  4. Set Visibility to say which way the rule runs. Visible shows the block only to readers who match, and removes it for everyone else — the usual choice. Hidden inverts it: readers who match lose the block and everyone else keeps it, which is how you show a subscribe pitch to non-subscribers only.

Per-block restrictions need Audience Management switched on, and nothing else — in Custom mode a block needs no content gate at all. If Audience Management is off, restricted blocks render to everyone. Anyone who can edit the post always sees every block, so check the result while logged out.

A Group block selected in the post editor with the Access control panel open in the sidebar, setting the block's gate to Premium Articles so only subscribers see that section.

Still stuck? Post in #newspack-help on Slack.