Set up custom post types and fields

How to get there: Open Settings → Post types & fields.

Post types let you categorize posts into distinct kinds (such as Feature Request, Bug Report, or Question) and attach different custom fields to each type.

Creating a Post Type

  1. Click Add Post Type.
  2. Enter a name (e.g. "Bug Report", "Feature Request").
  3. Optionally check the boards this type should be available on (users can only pick the type when submitting on those boards).
  4. Click Save.

The new post type appears in the list. You can rename it with the pencil icon, delete it with the trash icon, or copy its direct submission link with the link icon.

Assigning post types to boards

Each post type has a Boards setting that controls which boards expose this type on the submission form. If a post type isn't assigned to any board, you'll see a warning marker; users won't be able to submit posts of that type until you assign at least one board.

To change board assignments, click Settings under the post type and toggle the boards.

Auto-assign categories

Each post type can be linked to one or more categories. When a user submits a post with that type, the selected categories are automatically assigned. Open the Settings section underneath a post type and check the categories to enable this.

Automatic assignment works even when Let visitors choose a category is off in Board settings → Customer posting → Form → Category. For example, set the Bug Report post type to auto-assign Bug, then turn visitor category choice off. Visitors see no category field, and their bug reports still get the Bug category.

If Require a category is on, a valid automatically assigned category satisfies that requirement. Visitors do not have to choose another category. When visitor choice is on, they can choose a category in addition to those assigned by the post type.

For visitor submissions, only categories allowed under Board settings → Categories are assigned. Deleted or excluded categories do not count toward the requirement. If the post type assigns no available category, use a preselected category or let visitors choose one.

Categories in the admin form

Admins can choose from all workspace categories, even when a board limits the categories visitors can use. The board's preselected category and Require a category rule still apply, including to API submissions. If no category is selected, choosing a post type preselects its first available category. You can change that choice. Switching post types updates the automatic preselection but keeps a category you chose yourself.

Categories assigned by the post type are still added when the post is saved. The board's display filters do not change, so assigning a category does not automatically make the post appear on every board.

Adding custom fields

Custom fields collect structured information from users when they submit a post of a given type. Each post type has its own set of fields.

  1. Click Add Field under a post type.
  2. Configure the field:
    • Name -- the label shown to the user (e.g. "Steps to Reproduce").
    • Type -- choose from:
      • Text -- a rich text editor (formatting, links, lists).
      • Textarea -- a multi-line text box. Optionally enable Rich text to upgrade it to the same editor as Text.
      • Dropdown -- a list of predefined options. Enter the options separated by commas.
      • Number -- a numeric input.
      • Checkbox -- a yes/no toggle.
    • Required -- when checked, users must fill in this field before submitting.
  3. Click Add.

Fields appear on the post submission form whenever the user picks that post type. Edit a field with the pencil icon, delete it with the trash icon.

Reordering fields

Each field row has a drag handle (the dotted icon on the left). Drag fields up or down to change the order they appear in on the submission form. The new order is saved automatically.

Who can see custom field values

Custom field values are shown on the post detail page to anyone who can see the post, not just admins. If the post is public, members and anonymous visitors will see the field values. If the post is internal (see Internal Posts), only admins see the post at all, so only admins see its custom fields.

There is no per-field admin-only toggle. If a field should never be visible to end users, don't put it in a custom field, use an internal tag or an internal comment instead.

Each post type has a copy-link button that gives you a URL like /new?post_type=123. Share this link to send users directly to the new-post form with that post type pre-selected.

Setting custom field values via the API

Custom fields are supported on the REST API. When you create or update a post via POST or PATCH on /api/v1/posts, send two parameters:

  • post_type_id (integer): the id of the post type that owns the fields.
  • custom_fields (object): a map of <field_id>: <value> pairs. For dropdowns, send the option string. For checkboxes, send "1" or "0".

Example:

curl -X POST "https://your-portal.example.com/api/v1/posts" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Login button fails on Safari 17",
    "description": "Repro steps below.",
    "post_type_id": 42,
    "custom_fields": {
      "101": "Safari 17.4",
      "102": "iOS",
      "103": "1"
    }
  }'

The field ids are shown in the admin UI next to each field, and can also be listed via GET /api/v1/post-types/{postTypeId}/fields. Values are returned on the post payload under the same custom_fields shape on subsequent GET /api/v1/posts/{id} calls.

See Use the ProductLift API for authentication and rate limits, and the full endpoint reference at developer.productlift.dev.