Restrict Access at lower levels of product hierarchy
We need to be able to restrict access at lower levels of a product hierarchy. e.g. Reviewer at BU & Division, Product Owner for Product 1, None for Product 2.
Our hierarchy is BU -> Division -> Product Line -> Product. We want everyon...
Wes Gillette
almost 8 years ago
in Account settings
1
Unlikely to implement
Right now custom tag field only support renaming and deleting tags. You cannot replace a tag with another one, so essentially you are unable to merge tags. In contrast, 'OOB' tag field supports this capability.
Add an ability to Follow All of the support articles
I haven't started following individual articles yet but have noticed changes to some of the articles I reference frequently. Instead of going through and following various articles individually, I'd enjoy the ability to Follow All. As an Aha! SME,...
Guest
about 8 years ago
in Account settings
0
Unlikely to implement
Hi, our company has only 2 letters (Qt) and I'd like to use these two letters for the custom domain qt.aha.io. Which would be cool since our official domain is qt.io :) So for the form requires 3 letters :( Could you change that?
Guest
about 8 years ago
in Account settings
0
Unlikely to implement
Limit home page options to pages allowed for navigation
If I configure my portal to not display certain pages in navigation, then a user should not be able to select those pages as their home page. For example, I removed access to the Product tab for all users (as we officially define the data to appea...
Chris Steffen
almost 9 years ago
in Account settings
0
Unlikely to implement
Allow customization of fiscal years by product line or product
Currently, you can set the fiscal year at the account level. This makes sense if all product lines and products will fall under the same company. But it does not make sense when you're managing products for multiple companies within the same Aha! ...
Simon Smith
almost 9 years ago
in Account settings
0
Unlikely to implement
As a consultant with multiple clients using Aha, I want to login to each specific Aha instance (company1.aha.io, company2.aha.io, etc) with the same, professional email address.
I also want to manage support requests related to multiple clients fr...
Don't require Admin permission to create Products or Product Lines
As an Admin, I need to control who has a Paid Seat or not, to control costs. However, if a user has a Paid Seat, I don't care if they create Product Lines or Products, and I don't want to have to create the Product Lines and Products for them. For...
We want to have one Aha product linked to two different Jira projects. I've got this setup and working, but the Actions button simpy shows "Send to Jira" for both. It's challenging for users to know which one is appropriate for which project. It w...