Skip to Main Content
Status Future consideration
Categories Reports
Created by Guest
Created on Aug 7, 2019

Password protection for "Share as webpage"

Previously, we heavily used the "notebooks" feature to publish a scrollable webpage view of our feature lists for our Engineering teams that we didn't want to give access to our main Aha account. Now that "notebooks" have morphed into "presentations", this experience became noticeably difficult.

I discovered today that there's now an option from the List Report to "Share as webpage", but this unfortunately does not allow us to protect it with a password; we don't want this information to be accessible to the general public.

My workaround until this feature is available is to download each of our 9 list reports as an image and republish in Confluence each time I make updates to the list; this will take substantially more time and effort.

Please add the capability to define a password per shared webpage! This would be most useful to us if we could set a password for each shared webpage, versus for one password that impacts all shared webpages. I can easily imagine it being a new option in the attached screenshot of the current settings modal that appears when you choose to share a list.

    Oct 31, 2022

    You can now enable single sign-on for shared webpages in Aha! Ideas and Aha! Roadmaps. This gives you even more control over the way you share your product development plans.

    We will keep this idea open to keep monitoring feedback on the ability to define passwords for shared webpages.

  • Attach files
  • Jeff Clark
    Nov 12, 2022

    Great to see this added, thank you!

    I've enabled, but there was no feedback that it was enabled, nor additional steps to take after selecting "Update sharing security", how can I tell its been enabled? Access a Roadmap webpage from a personal computer/email?

  • Guest
    Jul 5, 2022

    Must have, agree with all the comments. This places a significant barrier in our plans for our we hoped to use Aha! internally and could limit it's success.

  • Kim Smit
    Feb 3, 2022

    Agree that this is a must have.

    I need the ability to share report & roadmap links to internal employees only. Without it, we are forced to view reports & roadmaps in Aha. This then prevents us from controlling what fields a viewer does and does not have access to, which is a HUGE blocker in our use of the tool.

  • Jeff Clark
    Jan 20, 2022

    This is critical, as sharing company confidential is of course a risk. We've tried to use the Presentation to share, but the shareable webpage UX is much more presentable/usable than the Presentation view.

    Hope Aha and work on this ASAP!

  • Elena Wood
    Jan 19, 2022

    The same applies to dashboards. They are a brilliant feature, but can not be fully used without SSO login similar to that set up for Presentation sharing.

  • Suzie McCarthy
    Jan 14, 2022

    Agreed. Adding password protection option for anything shared as a webpage would allow a significant increase in our use case.
    Example- we would like to be able to share a report of proxy votes with accompanying rational out to a particular customer. This is somewhat sensitive information since it relates to internal deliberations by a customer council. We would like to be able to send this as a linked report- so that they can simply refresh it after the council meets. Adding a password that could be changed periodically gives an additional layer of security to this report. Without that our council would be concerned that the link could just get pasted someplace for anyone to see. Therefore we have to now download the reports and manually shared them.

  • Daniel Lynch
    Jan 13, 2022

    I'd prefer SSO please.

  • Guest
    May 25, 2021

    This is a must have!

  • Julius Schneider
    May 25, 2021

    SSO (or password protection) would be great to have here, since sharing only data that does not need protection (also legally, if it contains any slightly personal information like guaranteeing this for reports is not really possible.
    Very unfortunate this feature is basically a legal risk waiting to happen (if in any displayed field contains sb's personal data).

  • Guest
    Jan 7, 2021


  • Steffen Moorrees
    Oct 22, 2020

    The webpage is a perfect way of embedding it in our internal sharepoint. But without any form of protection (Preferably SSO) or otherwise username/password protection the information is a bit to easily accessible for outsiders.

    Embedding a report or creating a screenshot is just not the same experience. So hopefully this is one that will make it on the 'to develop' list :)

  • Guest
    Jun 22, 2020

    Password or even SSO to protect "Share as webpage" is a must to provide us the ability to protect the information that should not be share outside of the org.

  • Chris Augustine
    Jun 17, 2020

    Yes, totally agree, would REALLY like to see password protection added to this. The publish as webpage option is far superior to the presentation/"slide" view for sharing reports that are longer than a single page/slide or especially wide (lots of columns) -- which, honestly, is most reports period.

    The slide view is very limiting and a web page is so much easier to both distribute and read, but we have major concerns about exposing the information publicly/externally. Please add a password option!

  • Jan Diep
    Mar 5, 2020

    Agreed. It is important to restrict access to specific stakeholders, and especially so that the data can't be shared externally accidently.

  • John Michaels
    Jan 13, 2020

    Yes, our organization sees great value in being able to share views internally ONLY within our organization using this "Share as a WebPage" if only there was a way to lock it down so only people within our organization could see it.  At this point, we have no way to do that. 

  • Guest
    Dec 2, 2019

    The web page is a better user experience as well. All the above points are totally valid. 

  • Jiyaad Naeem
    Aug 8, 2019

    Yes, we want to share certain pages with only certain stakeholders, but want them to be protected so they aren't readily available

  • +2