You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As it is today the available permission sets are;
ADMIN_ROLES
DALLE_ROLES
GPT_ROLES
TRANSLATOR_ROLES
SEARCH_ROLES
INDEX_ROLES
CHANNEL_CHAT_ROLES
CHANNEL_INSTRUCTION_ROLES
CHAT_BYPASS_ROLES
Describe the solution you'd like
A permission group to delineate between models. Eg have a permission group GPT3_ROLES and another GPT4_ROLES
Additional context
Since model is an attribute that can be set in a converse, any user can override GPT-3.5 which may be the more cost-effective role. While you could just go into the source and remove GPT4 as an available model, that would lead to no one being able to leverage the more expensive model as required.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
As it is today the available permission sets are;
ADMIN_ROLES
DALLE_ROLES
GPT_ROLES
TRANSLATOR_ROLES
SEARCH_ROLES
INDEX_ROLES
CHANNEL_CHAT_ROLES
CHANNEL_INSTRUCTION_ROLES
CHAT_BYPASS_ROLES
Describe the solution you'd like
A permission group to delineate between models. Eg have a permission group GPT3_ROLES and another GPT4_ROLES
Additional context
Since model is an attribute that can be set in a converse, any user can override GPT-3.5 which may be the more cost-effective role. While you could just go into the source and remove GPT4 as an available model, that would lead to no one being able to leverage the more expensive model as required.
The text was updated successfully, but these errors were encountered: