langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-27 03:01:54 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Can't view knowledge bases on Dify's cloud though the account owner has granted me access to the workspace as an admin #7444

New Issue
Closed
opened 2026-02-21 18:20:37 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 18:20:37 -05:00
Owner
Copy Link
Copy Source

Originally created by @blacktail on GitHub (Dec 30, 2024).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.14.2

Cloud or Self Hosted

Cloud

Steps to reproduce

On the cloud platform,

  1. Account owner granted admin access to another user
  2. The user login to the Dify cloud
  3. Go to the knowlege bases page https://cloud.dify.ai/datasets
  4. Can't find any knowledge bases there, but if login using the owner email, i can see there are many knowledge bases.

✔️ Expected Behavior

The user can view and manage the knowledge bases after the owner granted the admin access to the user.

❌ Actual Behavior

The user can't view and manage the knowledge bases after the owner granted the admin access to the user.

Originally created by @blacktail on GitHub (Dec 30, 2024). ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.14.2 ### Cloud or Self Hosted Cloud ### Steps to reproduce On the cloud platform, 1. Account owner granted admin access to another user 2. The user login to the Dify cloud 3. Go to the knowlege bases page https://cloud.dify.ai/datasets 4. Can't find any knowledge bases there, but if login using the owner email, i can see there are many knowledge bases. ### ✔️ Expected Behavior The user can view and manage the knowledge bases after the owner granted the admin access to the user. ### ❌ Actual Behavior The user can't view and manage the knowledge bases after the owner granted the admin access to the user.
yindo added the 🐞 bugcloud labels 2026-02-21 18:20:37 -05:00
yindo closed this issue 2026-02-21 18:20:37 -05:00
yindo commented 2026-02-21 18:20:38 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 30, 2024):

Hey @blacktail, I'm here to help you with any bugs, questions, or contributions! Let's squash those bugs together and make Dify even better 🐞

I found a similar unsolved discussion regarding visibility issues with knowledge bases in Dify. In that discussion, an admin and owner couldn't see a knowledge base created by a colleague who had left the company [1].

In Dify, access to knowledge bases is controlled by visibility permissions, which can be set to "Only Me," "All team members," or "Partial team members." Even as an admin, you might not have access if the knowledge base is set to "Only Me" or if you are not included in the "Partial team members" list [2].

Additionally, the 'admin' role in Dify allows for the creation of knowledge bases, but there is no specific mention of permissions to view or manage knowledge bases created by others unless explicitly granted [3].

It might be worth checking the visibility settings of the knowledge bases or confirming with the account owner that the permissions have been correctly set to allow admin access.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot[bot] commented on GitHub (Dec 30, 2024): <!-- Greeting --> Hey @blacktail, I'm here to help you with any bugs, questions, or contributions! Let's squash those bugs together and make Dify even better 🐞 <!-- Answer --> I found a similar unsolved discussion regarding visibility issues with knowledge bases in Dify. In that discussion, an admin and owner couldn't see a knowledge base created by a colleague who had left the company <sup>[[1]](https://github.com/langgenius/dify/discussions/8518)</sup>. In Dify, access to knowledge bases is controlled by visibility permissions, which can be set to "Only Me," "All team members," or "Partial team members." Even as an admin, you might not have access if the knowledge base is set to "Only Me" or if you are not included in the "Partial team members" list <sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/guides/knowledge-base/knowledge-and-documents-maintenance.md)</sup>. Additionally, the 'admin' role in Dify allows for the creation of knowledge bases, but there is no specific mention of permissions to view or manage knowledge bases created by others unless explicitly granted <sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/en/guides/management/team-members-management.md)</sup>. It might be worth checking the visibility settings of the knowledge bases or confirming with the account owner that the permissions have been correctly set to allow admin access. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/f678607b-62a5-4bb1-8bca-6de1ceb9654e?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/f678607b-62a5-4bb1-8bca-6de1ceb9654e?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/f678607b-62a5-4bb1-8bca-6de1ceb9654e?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/f678607b-62a5-4bb1-8bca-6de1ceb9654e?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f678607b-62a5-4bb1-8bca-6de1ceb9654e?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/f678607b-62a5-4bb1-8bca-6de1ceb9654e?feedback_type=other)</sup>
yindo commented 2026-02-21 18:20:38 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 30, 2024):

There is another settings you should check.
image

@crazywoola commented on GitHub (Dec 30, 2024): There is another settings you should check. <img width="999" alt="image" src="https://github.com/user-attachments/assets/ebbbc5e7-a2f8-4212-b16d-b94ee3dbd767" />
yindo commented 2026-02-21 18:20:38 -05:00
Author
Owner
Copy Link
Copy Source

@Fedrickson00 commented on GitHub (Dec 31, 2024):

i just got assisted on TIKTOK with the assistance of Xiaospy1 Platform.

@Fedrickson00 commented on GitHub (Dec 31, 2024): i just got assisted on TIKTOK with the assistance of Xiaospy1 Platform.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label cloud 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#7444
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?