Feat Req: Thoughts on improving API Key Management (Inspired by Anthropic)

[erhanurgun]

While I was on the Anthropic API key management screen, the idea came to me that it would be nice to have some of the features found there in VitoDeploy as well...

To summarize them as features:

1. Even if the entire API key isn't visible, showing a portion of it under the given name would help in verifying what it is used for without deleting it, even if the API's name is forgotten.

2. Including information on who created the API key would make it more manageable for large teams.

3. Including information on when it was last used would provide us with details on whether it is currently active or if it has been used before.

4. Perhaps most importantly: The API key can be set to a passive state with a single click when desired, without the need to delete it. It can be enabled again later when needed.

5. Another feature that isn't in the Claude API table but I think would be nice to have is: the ability to change the API's permissions... This way, an API key can be managed from here without needing to be changed in other projects. You might not add this if you think it could create a security vulnerability... But then again, anyone who can access this is already an authorized person, so I don't think it would be a problem!

6. BONUS: It would be nice to be able to sort ASC, DESC by clicking on the relevant column header in the table... In fact, it would be even better if this feature existed in all of VitoDeploy's tables!

So, what do you think about this? Don't you think it would make Vito's API management better?

---

VitoDeploy SS:

Anthropic Console SS: