What changed
On November 10, 2026 Ghost introduced custom fields for member profiles. Staff can define short text, long text, single/multiple-choice lists and address fields, populate them manually, through CSV import, Admin API or Zapier, and filter and export member records by these attributes. Fields start private; staff may expose selected fields to members through Portal profiles. Ghost(Pro) makes the feature available on Publisher plans and above.
Why it matters
Independent publishers and paid communities can capture company, region or interest information inside their membership system rather than synchronising a separate spreadsheet or lightweight CRM. The ability to filter members and save views makes audience management more useful, while API access permits integrations. But collection is a post-signup workflow, not a replacement for onboarding forms, and exposing imported personal data to members demands care.
Member data is now structured inside Ghost
The November 10 release supports short and long text, address and configurable choice lists, including multiple selections. Fields are created in Settings → Custom fields, and values can be populated by staff, CSV import, Ghost Admin API or Zapier. Saved member filters can segment records by custom attributes and the data appears in normal member exports.
Portal controls visibility, not initial signup
All fields start private to staff. When a field is marked visible to members, members can see and update it in their Portal profile, including values imported earlier. Ghost's current documentation says neither Portal signup nor embeddable signup forms collect these fields; fields cannot be mandatory. Publishers must explicitly invite existing members to fill them in after registration.
Schema and deletion rules matter
Field type cannot be changed after creation, and existing list choices cannot be edited in place. A blank CSV cell does not clear an existing value. Archiving hides the field from further member editing but retains saved data and existing filters; archived fields are omitted from member exports. Deleting an archived field permanently deletes associated member data. These rules call for careful field design and export procedures.
Plan boundary and operational questions
Ghost states custom fields require the Publisher plan or higher on Ghost(Pro). The public release and help documentation establish the feature's behaviour but do not independently establish performance at large membership scale or every self-hosted-version compatibility boundary. Operators should verify their installed Ghost version and API integration before migration.