I’m trying to understand the effect of the “Disable user API keys” setting in the OpenAI Platform’s Organization settings > Access Control section.
The description states:
“Disable user-based API keys across your entire organization. You can also choose to disable them on a project-by-project basis if needed.”
However, even after enabling this setting, user-linked API keys do not appear to be disabled.
Could someone clarify what this setting actually does? Does it prevent the creation of new user API keys, or should it immediately disable all existing ones?
Disabling an API key should lead exactly to the expected result.
Sometimes it can take a short while for all systems to properly respond to the new state.
If the key still remains usable, please send us an update.
Perhaps there is a misunderstanding based on the language you are using.
“user keys” in this case are the original API key style, They start with only “sk-”. They are not project keys, but are keys connected to a user profile, which the organization to which they are billed can be switched. “legacy” keys, which new user accounts don’t even have in their API platform user interface.
