Fieldnote Members · Product walkthrough

See a membership become protected access.

Follow the complete Fieldnote Members lifecycle—from a published offer to a real member session and server-enforced access to protected editorial value.

Choose another role Public plans

Lifecycle proofOne person. Five linked states.

OfferFieldnote Monthly

Published

Membership + entitlementActive access

Server enforced

Protected valueThe Margin Brief

Available now

Read-only demo boundary active

What this demo proves—and what it does not

Real product behavior, honest external boundaries.

This demo uses app-owned sessions and durable local records. Shared business records are read-only.

PaymentsUnconfigured
Outbound emailUnconfigured
Live webhooksUnconfigured

The product spine

Follow the value, not a feature checklist.

Each step has its own record and rules, but the member experiences one continuous journey.

01
Publish a plan
A clear offer becomes publicly joinable.
02
Join
A person enters through an app-owned account flow.
03
Create membership
The commercial relationship is recorded separately.
04
Grant entitlement
Server rules decide which value can open.
05
Open protected value
The member reaches the editorial experience.

Choose a perspective

Enter where your evaluation matters most.

Every journey uses the same app-owned login and server-side role boundary as the real product.

Recommended first

Member experience

Start with the product's must-love role and open the protected value the membership grants.

Member Home
Protected reading
My Access
Membership
Billing

Owner workspace

Trace the same lifecycle through plans, members, access, payments, reports, and provider truth.

Overview
Plans
Members
Access
Payments
Reports
Integrations

Specialist roles

Inspect the handoffs behind the member experience.

Choose the role closest to the operational decision you want to review.

Start with the member

See the promise before inspecting the machinery.