# Ghost adds member custom fields, but signup forms cannot collect them yet

Ghost's November 10 member custom fields bring editable profile data, audience filtering and API access into its publishing stack. Publisher-tier access, post-signup collection and immutable field types shape adoption.

Ghost now stores typed member attributes with Portal self-service, CSV import and API updates. Publishers gain simpler segmentation, but cannot require fields or collect them at signup.

- Status: Active
- Published: 2026-11-13T21:35:05+13:00
- Updated: 2026-11-13T21:35:05+13:00
- Categories: Marketing & Distribution, Content & Publishing
- Tags: API, Ghost, members, publishing, segmentation
- Canonical HTML: https://beyondthe.news/dossiers/ghost-member-custom-fields-portal-api-csv-limits-november-2026

## 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.

## Key details

- Announced November 10, 2026 in Ghost's changelog.
- Four field types: short text, long text, list and address.
- Member-facing fields are opt-in; imported values become visible when exposed in Portal.
- CSV import, Admin API and Zapier support field values.
- Custom fields are not collected during signup and cannot be required.
- Field types are immutable; archiving retains data but removes it from exports.
- Ghost(Pro) access begins at Publisher tier.

## Builder takeaways

- Design the field schema before importing members because types cannot be changed later.
- Use Portal profile links and follow-up messages to request optional information after signup.
- Audit any imported sensitive values before toggling fields visible to members.
- Test CSV import, export and deletion semantics on sample members before relying on the feature for CRM synchronisation.
- Check Ghost(Pro) plan eligibility or self-hosted deployment compatibility rather than assuming universal access.

## What to watch

- Whether Ghost adds signup-form collection or required fields.
- Future controls for changing field types and list choices.
- Clarification of self-hosted minimum version and scale limits.
- Whether segmentation gains direct automation triggers based on custom-field values.

## Uncertainties

- No independent reliability benchmark or migration case was found.
- Official documentation does not establish the feature's self-hosted version floor.
- Ghost does not currently support required fields or collection at signup.

## Sources

- [Custom fields](https://ghost.org/changelog/custom-fields/) — Ghost Changelog · official_announcement · 2026-11-10T00:00:00+13:00. Primary release announcement and feature description.
- [Custom fields — Ghost manual](https://ghost.org/help/custom-fields/) — Ghost · official_documentation. Detailed plan eligibility, field types, member visibility, CSV, export, deletion and signup limitations.
- [Ghost custom fields community discussion](https://forum.ghost.org/t/custom-fields-ghost-changelog/64182) — Ghost Forum · direct_statement. Public project-community discussion of the release; not independent performance validation.

