Make notebooks more interactive, especially for roadmaps

I often share the "roadmap" slide of a notebook via the web URL. The basic feature name is there (and we can include our custom field "user story" if we want), but I'd prefer it if the features were all clickable, and some basic information about each feature would be displayed on click.

The major usage case would be to publish the roadmap internally, but allow users to click on a given feature to learn more about it (as the title alone can be confusing to those who aren't actively talking about the feature).


User story: as a stakeholder without an Aha account, I want to be able to click on items in the roadmap for more information, so that I can stay informed about what features are coming in the product.

  • Jason Slaughter
  • Jun 3 2015
  • Unlikely to implement
Release time frame
  • Jan 8, 2016

    Admin Response

    Notebooks are an excellent tool to share information with key stakeholders on roadmaps and additional product management activities. Notebooks can be published to a secure web page and can be shared with anyone. As you make changes in Aha!, they can be automatically updated in your Notebook so that you do not need to update information in multiple places.

    We can understand the potential benefits of making features and other items clickable through a notebook. That said, there are permission related issues with this idea. 

    Notebooks are available to all users, but information within the application are only available to application users. 

    One potential workaround would be to include Feature detail pages within the Notebook to allow for easy access on important features (or other details which you would like to share).

    At this time, we are unlikely to make changes in this area because of user permission limitations and current priority areas. We hope you can understand.

  • Attach files
  • Avigail Ehrenhaus commented
    November 4, 2015 15:25

    This is really important for us.

  • Robi Chakrabarti commented
    November 5, 2015 18:39

    Now that we have multiple teams in the organization using Aha we are starting to run into the challenge of having a lot of reports and views. I would like to be able to provide one central place for people to see reports in a way that lets them interact with the various reports as needed. Notebooks are great for presentations but since they're not interactive they don't quite meet my need.

    A specific example - we have a Widget Timeline report, a Widget Release roadmap, and two other release roadmaps that our Widget product is a part of. I'd like to be able to collect these 4 reports in one location so anyone interested in Widgets (and what they're working on) can have both the high-level and feature-level view, as well as see the larger picture of what the Widget product is involved in.


  • Iam Williams commented
    February 22, 2016 01:56

    This is one of our biggest frustrations with an otherwise very solid product. Even the ability to see/expand the description would be helpful. With lots of features the condensed views are nice but often folks want to see a description to help contextualize it more.

  • Sohini Chaudhuri commented
    May 11, 2016 22:47

    This is a big issue for my organization. We can control permissions by publishing links to specific individuals but not being able to drill down deeper Features, Roadmaps etc is very frustrating.

  • Rob Oesch commented
    June 10, 2016 17:43

    How about clickable links to the outward facing Ideas Portal?  We are encouraging stakeholders to submit ideas and vote on others.  However, we are missing the connection between showing them reports of Ideas and then interacting with them.  A clickable link for the Idea URL field would solve this problem in the Notebook.  More details in this Idea -

  • Guest commented
    October 14, 2016 18:07

    This is a great idea. Many Sale teams still favor PowerPoint for presentations but this idea would one up PowerPoint and help motivate a "switch".

  • Derek Bambach commented
    June 6, 2017 17:57

    Lots of our notebook users are set up as "reviewers" so there isn't much of a permissions concern. It's not so hard to through up a "You can't access that" message. This would be super useful because it is hard to get the senior leadership to care about learning the whole UI and where to find the proper information. The notebooks give them a "curated" version of the content which is much better, but then they can't add comments or input via discussion because it's too much effort to go find some item in the app that they saw in the notebook.

  • Jonathan Mathews commented
    July 10, 2017 17:57

    I just created another idea related to this. If you have a list of ideas in an Aha notebook, then the Idea score is hyperlinked, but the idea itself is not, which is a little strange.

  • Ross Tanner commented
    July 26, 2017 16:09

    I get the challenges and concerns related to permissions. Still, there are a couple of clear paths available. 1) Share only strategic details, descriptions and such.  This would be great for published road maps. 2) Enable a login at any attempt to drill in. Then for selected objects enable the right side fly out within the notebook.  I'm sure there'll be more to it but this one capability would provide a standard behavior that would be broadly applicable across many objects.

    In my organization we have all but stopped using notebooks because of the inability to drill into road map details. This is a very significant limitation for us, please reconsider.   

  • nick bunte commented
    February 23, 2018 15:43

    This is asked for daily. You should work through the permissions flow - perhaps we can just toggle this function in the settings - and then restrict by aha user. 

    If I am presenting a notebook to my execs and they want us to "drill down" there is zero permission problem. 

  • Sam Richards commented
    August 28, 2018 17:40

    One more emphatic vote for interactive notebooks. This would be incredibly useful for our team to be able to click on a feature in a view in a notebook and be able to see details or even limited information (e.g. Description).

  • Guest commented
    October 8, 2018 15:37

    If you click through, you are forced to log in and face standard Aha permissions. I don't understand why providing the link breaks that protocol.