Originally created by @Zeta-ZhaoLi on GitHub (Jul 3, 2024).
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
No.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Every user should be able to set their own API Key, use their own quota.
Or even further more, add the quota data, and add a price data for every model (charge for tokens or requests), then will be able to limit the usage for every user. So that the admin can only set the main Key.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Every user use their own Key should be easy to modify the system.
Additional context
Add any other context or screenshots about the feature request here.
We all know the long chat costs quota a lot, there should be a way to limit every user, or even just know everyone's usage.
The road map mentioned a finely control access level, but no specific describe, if my issue already in your plan, just ignore this.
Originally created by @Zeta-ZhaoLi on GitHub (Jul 3, 2024).
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
No.
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
Every user should be able to set their own API Key, use their own quota.
Or even further more, add the quota data, and add a price data for every model (charge for tokens or requests), then will be able to limit the usage for every user. So that the admin can only set the main Key.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
Every user use their own Key should be easy to modify the system.
**Additional context**
Add any other context or screenshots about the feature request here.
We all know the long chat costs quota a lot, there should be a way to limit every user, or even just know everyone's usage.
The road map mentioned a finely control access level, but no specific describe, if my issue already in your plan, just ignore this.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Zeta-ZhaoLi on GitHub (Jul 3, 2024).
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
No.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Every user should be able to set their own API Key, use their own quota.
Or even further more, add the quota data, and add a price data for every model (charge for tokens or requests), then will be able to limit the usage for every user. So that the admin can only set the main Key.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Every user use their own Key should be easy to modify the system.
Additional context
Add any other context or screenshots about the feature request here.
We all know the long chat costs quota a lot, there should be a way to limit every user, or even just know everyone's usage.
The road map mentioned a finely control access level, but no specific describe, if my issue already in your plan, just ignore this.