RELATED IDEAS
Make admin access multi-level by organization/product line
We have multiple organizations/Business Units/Groups with their own product line in the hierarchy. We would like to be able to make them admin of just that area so that they can make the customizations they need without negatively impacting products they do not have/need access to.
| Release time frame | 1 month |
-
ADMIN RESPONSEAug 15, 2019
Enterprise+ customers can now create and assign custom roles for their users.
Account roles grant access to specific pages within account settings.
Workspace roles grant access to specific workspace features and settings.
Read more about custom roles on the support site: https://support.aha.io/hc/en-us/articles/360031941712.
We will continue to monitor feedback on this idea.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +9
1
MERGED
Customization at Product line instead at account level
Currently customization like custom fields, custom layouts are all visible to all users who have access to customization. As each Aha instance is used by multiple biz groups, providing customization access to any user means they have chance to upd...
0
Future consideration
22
MERGED
Ability to restrict customizations permissions to specific Product Lines and Products.
We would like the ability to restrict access to account customization settings to limit the product lines and products that a user can edit. By allowing users to only access customizations for specific product lines and products, this can allow us...
1
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved
I must say i agree with Caal, Guillermo (GE Digital) comment. The update doesn't adress the issue that was stated
Disappointed with your implementation. What you implemented is NOT what was being asked. This should be reopened.
Any update on this?
Super important for bigger organizations!
Product Owners have very different levels of understanding of the Aha! application, i.e. they do not necessarily know how changes they make affect other products. Also, in terms of standardizing e.g. Ideas Portal configuration, Integrations or use of Custom Fields and Workflows, it would be helpful to limit the customization that each PM can do.
In large structured organizations this is a major blocking factor to use a single domain company wide and will generate proliferation of multiple domain not communication each others.
blocking global adoption and instance consolidation
This is a must for big companies. This is now really critical to us, especially the Admin customization is very important. Why would members of a totally different Business Unit, would have capability to change customizations from other totally unrelated Business Units? Hopefully you can address this soon.