Feature Requests

I would like the Active Users access control screens to be enhanced in order to help manage access for our large organization. * Can we add projects and organizations that the users have access to (admin, collaborator, role bindings, user groups at that scope level)? We currently have to go to every organization and project (100s) to gather this * Can the last login date of the user be displayed * There is currently no way to filter the data. I would like to be able to filter by: * Name * Role Binding * Project Name * Organization Name * User Group * There is currently no way to export (filtered or unfiltered) results. This would help us generate regulatory responses efficiently

Needed support for delegate selector for webhook notification. Webhook notification uses delegate only if webhook url is type of secret. But there is no support for delegate selectors for the same.

I’ve written a large amount of software products where we were maintaining assets and we did this. While individual searches are “ok,” they simply are just not efficient. Having a top-level “search all the things” option is usually an absolute must. It also helps when people are extremely busy and half forget what they were looking for by type, but remember the name (we literally had a feature request for that reason for a search at one point). I’d envision something like the attached image:

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

Customer wanted this functionality :- 1.Let user create a new token with the same name if the prior one is revoked. Only restrict on the same active delegate token name. Delete revoked token immediately and a new token with the same name should be allowed.

We have a use case where we would like to give a user permission to view,create project level connectors but only view permission at org level connectors. This can't be done easily with the current structure of resource groups. The options I have are: only org level resources - does not give access to project level resources all resources including child scopes - give access to all resources at org and project level, no way to exclude org level resources specified project - is close to what is wanted in use case, can exclude org level resources The problem with specified projects, is there is no way to select all projects, instead you have to select all projects individually. This causes problems when projects are added and deleted to the org, this list must be maintained.

We would like the ability to create Dashboard Folders to be supported by the terraform harness provider.

Use cases include: Visualizing template usage across projects, including version usage, git branch usage, and nested template usage Use template tags to filter pipeline executions, to avoid tagging each project's instance of a pipeline using a pipeline template Ability to analyze templates based on their components, all templates that use SAM, all templates that use ServiceNow, all templates that are k8s, etc

Many users find excessive notifications irrelevant or overwhelming which hampers user experience. In our case users find too many notifications irrelevant for all the projects/environments. They care about notifications of specific environments like TST->STG, STG->PRD etc and there was no control over it in Harness. Our request is to create an Advance Notification System which supports : Granular Control : Allow users to enable/disable notifications. Provide options to adjust the frequency of notifications (daily, weekly, real-time etc). Users can mute notifications for a period of time (like going on vacations etc). Priority Level : Users can set priority level of notifications or put them in categories for ex users to set critical notification for PRD env and normal notification for TST or lower env. User profile : Notification control should be in the user profile for easy access and manageability.

Are there any plans on the roadmap to support Azure Federated Id Credentials? GitHub supports this feature, and it is very helpful in that case. It would be great if Harness could support it as well. The value of this feature to us would be we don't have to store Azure clientId/secrets in the Harness credential manager.