EchoInk

Our InkDocs are compilations of SOPs and a doc summary is not as useful as a page summary. We would like AI-created page summaries to be created for our pages instead of the entire document.

The navigation pane in the left panel lacks many user friendly features. Presently, it is too restrictive on only showing down to H2. Authors should have the option to show any header within the navigation hierarchy for ease of organization and ease of navigation for the end user. It should function similarly to the navigation pane in Word when you use structured headers. Additionally, the end user should be able to expand/collapse the headers under each page (presently they are permanently expanded) and should be able to expand more than one section at a time (presently if you expand a new section, the previously expanded section collapses). All-in-all it's a very clunky user experience that should be improved to support more intuitive and more efficient navigation.

When inkdoc content (in the the Knowledge Library or via habitat export) is published, it needs be in a format to inform/train AI knowledge agents or search tools such as Leena.ai

In addition to featured content, it would be great to automatically notify learners via email when SOPs or training guides have been updated. When a new version of an SOP or training guide is being published, a prompt can ask if the author would like to notify specific users, all users who have accessed the document, or all users. Users who have favorited an InkDoc would always get the notification. This will help ensure that users who impacted will have immediate access to updated docs rather than relying on featured content.

When a user encounters a login or access error, the system should immediately trigger a webhook event containing key error details. Proposed webhook payload fields: Date (required) Time (required) User (required) Account (optional) Error (required) Error details (e.g., message, stack trace) Purpose: The goal is to enable automated, real-time monitoring and response to user access issues without relying on manual reporting or exports. Support teams should be able to identify and act on errors as they occur—rather than waiting for user reports or delayed escalation. Benefits: Immediate visibility into login and access failures Faster troubleshooting and resolution Potential for integration with internal alerting, correlation, or support tools Ability to analyze recurring issues or patterns across users or institutions Alternative Approach: If real-time webhook delivery isn’t feasible, periodic exports or API access to a filtered error log stream could provide a fallback solution.

It would be nice to search within an individual chapter or within a page, instead of the entire Inkdoc. This is helpful because end users know which Inkdoc content lives in- down to the chapter and page. They just need to get more specific in search most of the time.

Users would like the ability to view the platform/content in Dark Mode.

In Reader View, From the Library tab, users would like the ability to view ALL of the notes they've made (across all InkDocs) and to be able to jump to that InkDoc/content when clicking on a specified note from their Library.

I would love to be able to add closed captions to videos without going through the EchoInk team. This would be a widely beneficial addition to the Habitat tools. This would make the process more efficient for our team and EchoInk team!

I would suggest this be applicable to all content, not just links. For example, if we need to find/replace a specific word or phrase, having the ability to easily do that throughout content would be much more efficient. Find/Replace links - ability to find and replace multiple links all at once (upon designation)