Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: CHAT CANNOT ACCESS TEAM KBs #4022

Open
1 task done
EzeLLM opened this issue Dec 13, 2024 · 2 comments
Open
1 task done

[Bug]: CHAT CANNOT ACCESS TEAM KBs #4022

EzeLLM opened this issue Dec 13, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@EzeLLM
Copy link

EzeLLM commented Dec 13, 2024

Is there an existing issue for the same bug?

  • I have checked the existing issues.

RAGFlow workspace code commit ID

765a114

RAGFlow image version

v0.13

Other environment information

No response

Actual behavior

I signup and add llm and do other configs. i get access to a team kb which i can see its contents when i make a search or when i click on it in knowledge bases. however, the llm is not getting access to it! when i try to ask a question i get the default answer for not found in knowledge base. however when i enter the user that is the owner of the knowledge base i can ask the llm the same question and it answers perfectly.

Expected behavior

No response

Steps to reproduce

try to chat using team kb

Additional information

No response

@EzeLLM EzeLLM added the bug Something isn't working label Dec 13, 2024
@KevinHuSh
Copy link
Collaborator

Do you add the KB for dialog setting?

@EzeLLM
Copy link
Author

EzeLLM commented Dec 13, 2024

I did add the knowledge base when creating the assistant in chat section. Is that what you mean?
But when the knowledge base is owned by other member in the team it always returns the default empty answer.
The same query retrieves successfully when sending from other user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants