RELATED IDEAS
Distinguish API key usage in history
We currently have two applications writing to Aha using 2 different api keys, but both under the same user.
It would be great to have a way to distinguish which api-key is used in the history tab of a record. Currently it only shows the user so a PM can't determine where the update came from, and from a governance/compliance view point we can't track.
We use 2+ API keys so we can easily revoke/regenerate one (eg, if somebody leaves) without requiring all apps to change. The apikey user also has cross account access which we don't want to give out generally, so being able to see which one is posting would be good.
Adding the apikey name to the username in the history tab would be really helpful.
-
-
- +1
Further to the above, we use 2+ API keys so we can easily revoke/regenerate one (eg, if somebody leaves) without requiring all apps to change. The apikey user has cross account access which we don't want to give out generally, so being able to see which one is posting would be good. As per the other comment, using the API key name would be a good solution.
Naming API keys, and reflecting the name of the API key in the audit (instead of the identity of the owning user) would be an awesome solution to this problem.