Determine default Home Page for All Users
When a user logs into Aha!, the first page they see is the page "How Aha! works". Our users are reporting that this is confusing, as they want to navigate to a page within the product itself (i.e. Feature Board or Releases Overview"). Users arriving on the "How Aha! works" page have to find out how to navigate into the product - so it takes a little while. For us it is critical for adoption of Aha! that executives and other company stakeholders be presented with a page that presents them with exactly what they need to see first - instead of having to find out how to navigate there.
So if a user hasn't already set their own home page, we would like to specify what the "default" landing/home page should be - other than the "How Aha! works" page. This is a helpful page, but more as a knowledge base/reference that someone would have to click into if they are looking for that kind of info.
-
ADMIN RESPONSESep 10, 2024
Set a default homepage for your colleagues
People look to you as the Aha! expert. So now, you can direct teammates to a default homepage. Select a key page or saved view — such as a product dashboard, note, or framework — to help the team quickly find essential information.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
21
MERGED
7
MERGED
2
MERGED
Being able to customise the home screen for multiple users/entire account
Hi there,
I hope you're well.
I would like to be able to change the home screen for our entire organisation.
I don't want users to be confronted with the 'messy' portfolio view when they first login to Aha as this is quite daunting and isn't reall...
0
Shipped
© 2025 Aha! Labs Inc.•All rights reserved
We have a similar usecase. We have an internal knowledge-base that explains AHA! is used for, whom is responsible for what, and which roles should be approached regarding which responsibilities.
This information is hosted internally and has links to other non-aha.io sources.
It would be awesome if we could set up a Default Home Page (or Default Landing Page) for all users that links to our kwowledge base, so our employees can get up to speed faster.
The vast majority of our Aha users are read-only (e.g. Sales, Management) that we'd like to see everything but who should easily find all they need from a "master dashboard". It would be great if that dashboard could be their home page. A CEO or a sales rep isn't realistically going to take time to go through a tutorial on how to navigate and customize their own "My Work" or Dashboards. They will log in to Aha, get confused, and still message Product people for all the answers.
Agree and support this idea, we have a mix of heavy Aha! users/light users. The ability to set default homepages and block the views out that are not applicable will greatly increase the adoption of the platform.
Very much agree that is a useful addition to get a standardized 'homepage' for all user; helps in consistent messaging...
This is incredibly important for us as we expand the use cases of Aha across multiple workspaces. Currently we intentionally disable certain navigation items that is irrelevant for a particular workspace. However if an user navigates from another workspace, it defaults to whatever page they originated from.
Example
Workspace 1 has only 'Roadmaps' enabled in navigation.
Workspace 2 has only 'Strategy' (goals/initiatives) enabled in navigation.
When use goes to 'Strategy' in Workspace 2, then navigates to Workspace 1, the default landing page is 'Strategy' in Workspace 1. Even though this is something we don't wish to expose.
Highly interested in this feature.
Would really love to see this implemented. I created a landing page on our workspace overview, and would love to make that the default landing page for everyone in our company given that it can be a dense tool to navigate. Please consider implementing this in the near future!
Absolutely agree! This is quite inconvenient especially when onboarding new employees who do not belong to the product organization but use Aha to review the roadmap.