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
when new user join the team, and try to ask question in chat, got following error:
Model(text-embedding-v3) not authorized
the kb's embedding model is text-embedding-v3 from Qwen, why can't the user use the team's API key ?
Expected behavior
new user can reuse teams embedding and chatting API:
first user create one knowledge base
first user config the embedding model for the new knowledge base
first user invite second user to the team
second user can use the knowledge base right away without needing to configure the model provider
Steps to reproduce
1. create kb and invite person to the team
5. new team member try to ask question in chat
Additional information
I think the logic will result in the #4379 confusion.
someone else seems to talk about this #2742 , but even with the team function, the second user need to config his own API to use the team's knowledge base
The text was updated successfully, but these errors were encountered:
someone seem to succeed with many use sharing same API in #2742 , but he seems to edit the database directly.
Is there any way of doing it in the web GUI?
Is there an existing issue for the same bug?
RAGFlow workspace code commit ID
NA
RAGFlow image version
c8d280849d25
Other environment information
No response
Actual behavior
when new user join the team, and try to ask question in chat, got following error:
the kb's embedding model is
text-embedding-v3
from Qwen, why can't the user use the team's API key ?Expected behavior
new user can reuse teams embedding and chatting API:
Steps to reproduce
Additional information
I think the logic will result in the #4379 confusion.
someone else seems to talk about this #2742 , but even with the team function, the second user need to config his own API to use the team's knowledge base
The text was updated successfully, but these errors were encountered: