How to get there: Click All Posts in the sidebar, 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. Each board can show a New Post button at the top and/or an always-visible sidebar submission form. Both are configured per board under Settings, Boards, Submission UI. See managing boards.
- Direct submission URL. Users can go to
/new on the portal to open the submission form.
- Widgets. Embedded feedback and changelog widgets 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.
What a post contains
Only the title is required for users. Everything else is optional and can be filled in later, either by the author or by an admin.
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 portal under Posting Defaults in any board's settings.
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. Search for an existing user or create a new one on the fly.
- Tags. Up to 20 free-form tags.
- Platform, Version, Release. Free-text metadata useful for changelogs and roadmaps.
- Prioritization scores. Impact, Confidence, Ease, and Reach values (0 to 100) used by the prioritization views.
- 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.
- Assigned To. Pick an admin user as the owner of the post.
- 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 moderation and publish immediately.
- 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 surfaced 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.