We’d love to see an approval-based workflow for creating Client Scoped and Global API keys.
Today, only our Super Admin can create API keys. Our current process requires users to submit a request through our internal helpdesk, and then our single Super Admin manually generates the key. This creates two challenges:
- It slows down users who are trying to build or integrate.
- It creates a bottleneck with a single Super Admin responsible for all API key creation.
A potential solution would be:
- Allow designated users (or regular admins) to initiate creation of Client Scoped or Global API keys within the Glean UI.
- Require Super Admin approval before the key becomes active.
- Provide clear visibility and audit logging of approvals.
This would maintain appropriate governance and security oversight, while significantly improving speed and reducing operational friction. It would also distribute operational workload without compromising control.
We believe this would be especially helpful for larger organizations where API usage is more frequent and centralized admin models create bottlenecks.
Would love to see this considered in a future release!
