Add the ability to control what modules are enabled on an org/project scope
long-term
O
Olive green Opossum
Currently, modules are enabled on a Harness account scope. Our organizations sometimes have different licensing needs, meaning some are licensed for more modules than others.
Managing this with a small number of organizations, while inconvenient, is manageable. But as the number of organizations grows, this becomes unmanageable.
Account administrators should have a way of configuring what modules a particular organization/project can use, and we should be able to track the license consumption per module across all scopes (Account/Orgs/Projects) to better estimate our licensing needs
Log In
P
Progressive Tyrannosaurus
We really need this capability for CCM only customers. It adds large amounts of confusion to users. At the very least, if permissions to say CD are denied/not granted, the module should be hidden from that user's view.
Prashant Batra
Noted Olive green Opossum. Thanks!
O
Olive green Opossum
Hi Prashant Batra — for #1 I think having the ability to turn on/off modules for our orgs would be a great start, e.g. org A is licensed for CI + CD + IACM, while org B is only licensed for CD, so every other module is disabled.
I don't think mapping licenses at the user/group level is a bad idea as it provides more granularity but our immediate concern is preventing orgs from using modules they're not licensed for
Prashant Batra
Roberto, Thank you for this suggestion. I see two clear motivations in this ask:
- Provide controls to do License Management - you would like to have some controls around who consumes a license.
- More granular License consumption reporting - be able to see license consumption at account / org / project levels.
Both of above make sense and will be considered as we build in coming quarters.
For 2, we already allow granular views of license consumption data at Account, Org & Project levels in our CD module. See under Account Settings -> Subscriptions -> Continuous Delivery. If this is in line with what you are thinking, this will come to all of our modules.
For 1, would it make more sense to allow license / module mapping at a user level?
Prashant Batra
long-term
Prateek Mittal
under review