Please tell us what we can do to make Featurebase the best product for you.
In Progress
Manage article access and unpublishing through API and MCP
Control Help Center article visibility and audience access through the API and MCP, and unpublish live articles without deleting them. This would let teams manage access and take outdated content offline from their own tools or AI workflows.
Hoverable glossary definitions in Help Center articles
Allow teams to define Help Center glossary terms and descriptions once, then automatically show the description when readers hover over matching terms in articles. This would explain terminology consistently without adding definitions separately to every occurrence.
Support browser translation for public Help Center articles
Public Help Center pages currently prevent browser translation of article content. Readers can see Chrome’s Translate option, but the article remains in its original language. Allow readers to translate public documentation using their browser’s built-in translation, while preserving necessary protections for interactive elements. This would make the documentation easier to use when a reader’s preferred language is not available.
Waiting on customer
Draft review and tagging workflow for Help Center articles
Let authors hand off a draft Help Center article to a designated reviewer, for example by tagging or assigning a reviewer on the draft so the reviewer is notified and can review and publish. Today there is no native review handoff, so teams draft in Google Docs first and copy the result into the Help Center, which creates two sources of truth. Raised by Securin during a demo (Nov 2, 2026). Product managers author articles and a technical writer reviews and publishes. Not a deal breaker, but it would remove the parallel drafting layer.
Read Help Center article analytics through API and MCP
Get Help Center analytics through the API and MCP: article views, reactions, and search terms, including searches with no results. This would let teams and AI agents find articles that nobody reads, articles with negative reactions, and missing content, and then keep the Help Center up to date from their own tools.
Update Help Center settings through API and MCP
Change Help Center settings through the API and MCP, such as the display name, title, description, search placeholder, navigation links, and visibility. Today these settings can be read through the API but only changed in the dashboard. This would let teams manage their whole Help Center from their own tools or AI workflows.
Image upload endpoint for Help Center articles
Provide a way to attach images to Help Center articles through the API, ideally a multipart upload endpoint that stores the file and returns a Featurebase-hosted URL for use in the article body. Alternatively, add multipart support to articles.create and articles.update, or confirm that base64 data URIs and external URLs in an article body are pulled into Featurebase storage as the changelog docs describe. Local screenshot files have no public URL, and embedding base64 bytes in the tool call is slow, error-prone and bloats the body, so the final step currently has to be done manually in the dashboard editor.
Support dynamic base URLs in the API playground
API documentation readers cannot currently enter a customer-specific base URL. Support reader-entered server URLs without requiring every URL to be listed in the OpenAPI spec. For embedded documentation, also allow the host application to pass the current site’s URL into the playground automatically.
Allow re-submitting Help Center Article feedback after article updates
Once a user submits feedback on a Help Center article, they cannot provide a new rating after the article is modified. Allow users to submit feedback again when an article undergoes material updates, so teams can measure whether recent edits improved the article's helpfulness.
Show article version for each feedback entry
Feedback entries and ratings on Help Center articles currently do not record which version of the article the reader was viewing. Track and display the specific article version for each feedback entry or score, so team members can tell whether negative ratings apply to an outdated version or the current draft.
Unlisted / link-only sharing for help center articles
Add an unlisted sharing option for help center articles, similar to Google Docs' "Anyone with the link can view" sharing feature. This is useful for API documentation for example.
In Progress
Unified knowledge management for Help Center and Fibi AI Agent
Knowledge is currently split between Help Center articles and Fibi AI Agent Training Data. They live in separate dashboards, use different content models, and cannot be searched, maintained, or automated as one source of truth. Create one Knowledge dashboard for all reusable support content, similar in concept to Intercom's Knowledge workspace. Common content types: public Help Center article, internal article, snippet, uploaded document, and external source. Choose where each item is used: Help Center, Fibi, and Copilot. An internal or Fibi-only article must never be publicly visible in the Help Center, but should be available to Fibi when answering. Unified management: search, filters, folders, bulk actions, and configurable columns for type, collection, audience, publication status, language, author, last updated date, and where the content is used. Consistent editing and lifecycle: one formatting model, drafts and publishing where relevant, source freshness, and clear ownership. Complete API and MCP coverage: list, search, create, update, delete, publish, and manage metadata for every supported content type. The goal is to stop treating public documentation and AI knowledge as separate systems. Teams should be able to create knowledge once, control who or what can use it, and maintain everything from one place.
Waiting on customer
Language-specific links and videos in auto-translated Help Center articles
I want to be able to use a different link or embedded video (for example a French YouTube video) per language in an auto-translated Help Center article, without breaking automatic translation for that article. Today, editing the translated version manually locks auto-translation for that article, so the workaround is a callout with a link under the German video or embedding all language videos in one article. Raised by PlaynVoice (German as base language, English and French auto-translated) during a demo on 2026-10-14, while they evaluate Featurebase against Intercom and Pylon.
In Progress
Disabling the Help Center should also stop article suggestions and public access
Today, "disabling" the Help Center only removes the module from the portal menu (Settings → Branding → Portal menu → Delete). The content itself stays live, so after disabling it customers still see: Articles suggested during ticket and conversation creation. Articles reachable and indexable on the public Help Center URL. The expectation is that deactivating a module makes its content and all linked functionality inactive, in one action. Requested behaviour A single workspace-level switch that takes the Help Center fully offline: no article suggestions in the Messenger or ticket forms, no public article URLs, no search-engine indexing. Apply the same principle to the other modules, so turning one off never leaves a surface still serving its content. Make the current behaviour explicit in the interface, since the existing control is a navigation change rather than a content switch. Current workarounds are partial: the Messenger Help module and article search card can be turned off individually in Settings → Support → Messenger → Customization, and articles can be restricted to Team members one at a time, which removes them from suggestions and search indexing but cannot be applied in bulk. Raised by a customer evaluating Featurebase who deactivated the Help Center and found the articles still active.
Support IP whitelisting for API spec fetching
Provide static IP addresses that organizations can whitelist so Featurebase can fetch API specs from URLs protected by IP restrictions.
Option to hide article action options
Add an option to toggle off article action options from user view in the help center to reduce clutter and prevent users from getting wrong answers via AI tools.
Segment-based access for individual API reference sections
Allow admins to restrict individual API reference sections or endpoints to selected user segments, like Help Center articles and collections. This lets teams keep some API documentation public while limiting other parts to specific users, without restricting the entire API version.
Help Center editor no longer allows text colors or highlights
The redesigned Help Center editor removes the Text color and Highlight text controls without a replacement. Users can no longer apply or change this formatting through the toolbar. Previously, both controls were available when selecting article text. Restore them or provide equivalent controls. Existing colored content remains supported.
Help Center-wide snapshot and versioning
Provide snapshotting or versioning for the Help Center as a whole, not just per-article history. Article-level version history already exists, but there is no way to restore the entire knowledge base after a destructive change. Broader team access combined with irreversible deletion makes an accidental mass wipe unrecoverable.