Skip to content
Office

Office Members feature

Protected content blocks

Put members-only content on your own site without it ever being in the page source.

Why hiding isn't protecting

Most membership scripts hide locked sections with CSS. The text is still in the HTML your server sends, so anyone who opens View Source, or any scraper, can read it. That's fine for a "Join now" banner. It isn't fine for the recipe, the lesson or the report you're selling.

How a protected block works

Write the content as a normal item in Members. On your page, add an empty element: <div data-m-content="celadon-recipe"></div>. When a member with access visits, the script asks our server for that item with the member's signed token and drops it into the page. Everyone else gets the preview and the unlock button. The full text never reaches their browser.

The hosted members area works the same way, so content there is protected by default.

Example

The same post, two visitors

Harbor Pottery's site has a /recipes/celadon page with the protected block. A signed-out visitor who opens View Source finds the page layout and an empty div. Jo, signed in as a Supporter, sees the full recipe with its gram measurements in the same spot. The recipe is stored once in Members, so editing it updates the site and the members area together.

How to set it up

  1. 1

    Create the content as an item in Members and set who can see it.

  2. 2

    Copy the embed line from the item's Share menu.

  3. 3

    Paste it where the content should appear on your site.

Protected content blocks is part of Office Members and included on every plan.

Questions people ask

Can you check my site for leaks?

A leak checker that loads your page signed out and flags members-only text in the source is coming soon.

Try Office Members with your whole team

7-day trial with every feature. Cancel from the billing page whenever you like.