Aha submitted this too fast: Description if someone who has the power to add this can!
Currently, API keys have to be generated at the individual user level.
Where this gets problematic: if the user who generated the API key that is connected to our Preset/DBT sync job leaves our company and is removed from Preset, that Preset/DBT sync will break. Because the code for the Preset/DBT sync is buried in the code maintained by one of our engineering teams, there's a good chance we won't understand why that broke ( i.e. the user who generated the API key is gone and with their account, the API key).
Ideally, there would be a location where any admin could generate an API key and that API key could be viewed by any other admins in the account. For a given token, they could "refresh the token" to generate a new secret if needed.
How does prioritization work these features might not have a lot of vote but don't we think these are basics ?
Aha submitted this too fast: Description if someone who has the power to add this can!
Currently, API keys have to be generated at the individual user level.
Where this gets problematic: if the user who generated the API key that is connected to our Preset/DBT sync job leaves our company and is removed from Preset, that Preset/DBT sync will break. Because the code for the Preset/DBT sync is buried in the code maintained by one of our engineering teams, there's a good chance we won't understand why that broke ( i.e. the user who generated the API key is gone and with their account, the API key).
Ideally, there would be a location where any admin could generate an API key and that API key could be viewed by any other admins in the account. For a given token, they could "refresh the token" to generate a new secret if needed.