How to get there: Click All posts (via a board’s breadcrumb or the sidebar shortcut, when available), then click the New Post button. Users can also submit posts from the portal at /new or directly from any feedback board.
Posts are the core content unit in ProductLift. Think of each post as a single piece of work, for example a feature request, a bug report, an idea, or a knowledge base article.
A post is connected to a board through its status, and it can collect votes, comments, attachments, references, and internal notes.
Where to create posts
There are several entry points, all of which result in a post under the same data model.
- Admin sidebar. Click All Posts, then New Post. This opens the admin form with every field available (status, category, tags, custom fields, assignee, dates, internal flag, and more).
- Board pages. If customer posting is allowed, the board offers a submit button or, for feedback boards on desktop, a form beside or above the board. Configure this under Board settings → Customer posting. Admins can create posts even when customer posting is off. See managing boards.
- Direct submission URL. Users can go to
/new on the portal to open the submission form.
- Widgets. Embedded feedback forms let users submit posts from your own product without leaving it.
- Import from file. Bring posts in from CSV or Excel. See importing posts.
- API. Create posts programmatically through the ProductLift API.
- Integrations. Tools like the changelog generator and connected services can create posts on your behalf.
On boards with a submit button, visitors are asked to log in before the form opens if an account is required. Closing that login prompt returns them to the board. Boards that allow anonymous posts open the form directly.
Some boards show the form directly on the page. Visitors can enter a draft there, but must log in before posting if the board requires an account.
What a post contains
The simple form requires a title. A board may also require a category or custom fields. Other details can be added later.
Fields available to users
- Title. Required. Between 2 and 180 characters.
- Description. Rich text with full formatting support. See formatting posts.
- Post Type. If the portal uses post types (for example "Feature" or "Bug"), the user picks one. Each type can show its own custom fields.
- Category. Optional, or required, depending on the board's posting defaults.
- Attachment. A single file can be uploaded with the post.
The exact labels for Title, Description, and the New Post button can be customised per board under Board settings → Customer posting. Changes apply only to that board.
Additional fields available to admins
Admins see the full form with these extra fields, grouped under collapsible sections.
- Status. Drives which board the post appears on.
- Section / Topic. For boards that use sections (such as a knowledge base), the post is filed under one.
- Author. Choose the person who made the request, or add them if they are new. When you record a customer's request, choose that customer instead of yourself. For feedback posts, the author can also count as a voter and follow updates. Roadmap items and some imports work differently.
- Vote on behalf. Optional. Add one or more existing users or new users as additional voters at the same time you create the post. Same UI as the vote-on-behalf flow on an existing post, but staged in the form and saved in a single request.
- Tags. Up to 20 free-form tags.
- Platform, Version, Release. Free-text metadata useful for changelogs and roadmaps.
- Prioritization. Use the prioritization workspace for the active scoring model and its criteria.
- Estimated Date. Target delivery date.
- Created At. Backdate a post when migrating content.
- Number of Votes. Manual bonus votes added on top of real user votes.
- Publish Status. Toggle between Published and Draft.
- Allow Comments. Per-post override of the board-level comment setting.
- Internal. Hides the post from browse, search, and direct URLs for non-admins.
- Assignment. Choose a team and one or more responsible people.
- Color. Free-form colour for RAG, priority, or any other categorisation.
- Excerpt. Up to 150 characters, used for previews and SEO. Auto-generated if left empty.
- Card Image. Image shown on the post card in board listings and changelogs.
- File Attachment. Any supporting file.
- Custom fields. Any fields defined for the active post type appear inline.
What happens after submission
The submission flow depends on the portal's posting and moderation settings.
- Admin submissions bypass customer moderation. Their published state and schedule determine when they become visible.
- User submissions can be routed through the moderation queue first. If a post is held, the user sees "Your post will be published after review". If a post is rejected by moderation, the user sees a warning notice instead.
- Notifications are sent based on the portal and per-user preferences (for example, admins can be notified of new posts, and the author is kept informed of status changes and comments).
- Duplicate detection runs as the user types the title. Similar existing posts are shown so users can vote on them instead.
Once published, a post is browsable on its board, picked up by search, and available through the API and webhooks.
Planning and assignment
For a new Gantt item, enter its planning dates and choose its type in the new-post form. A milestone needs one date; a bar needs a start and end date.
Admins can choose one team and multiple assigned people. Selecting a team does not select its members automatically. When you create from a specific board, the form already knows the destination, so it does not show a board picker.
See Create and manage a roadmap and Assign teams and people.