Skip to main content

Allow Projects to Limit Knowledge Base (KB) by Tags/Sources

Feature RequestChat Management/Interactions

Description:

Currently, only AI agents can be restricted to certain knowledge base tags or sources. There is no option to filter or limit which parts of the KB are accessible within a project’s settings. It would be much more efficient and secure if we could configure, at the project level, which KB folders or tags are visible/searchable during chats started in that project. This would simplify workflows for teams managing multiple projects with different information boundaries, ensuring users don’t see or retrieve irrelevant or confidential data.

Use Case:

Ensure users working in a specific project only access relevant documents.

Avoid needing to create dedicated AI agents for every project/Kb-combination.

Improve privacy, focus, and organization for teams with several overlapping datasets.

Suggestion:

Add a section in project settings to select which KB tags/folders are available in that project. Chats within the project would only search/retrieve those tagged documents.

1 comment

Log in to comment and vote

Comments1

  • Red Turtle

    •

    Mar 1

    This is a critical functionality that’s missing from project settings. It’s not just for teams, it is important for regular users…

    In my KB, I have a day-job tag with certain contexts, docs, etc. I also have a side-hustle tag with different docs, contexts, etc. I don’t need typingmind to search across both needlessly, it adds noise and token burn.

    When building, y’all can use the same tag filtering component from the Agent flow, just expose it in the Project settings page.