langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-23 04:55:28 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Users deleted from the workspace can still log in to Dify #2279

New Issue
Closed
opened 2026-02-21 17:43:50 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:43:50 -05:00
Owner
Copy Link
Copy Source

Originally created by @majestichou on GitHub (Apr 17, 2024).

Originally assigned to: @GarfieldDai on GitHub.

Self Checks

  • This is only for bug report, if you would like to ask a quesion, 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).
  • Pleas do not modify this template :) and fill in all the required fields.

Dify version

0.6.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I started the Dify service using docker and then accessed the Dify frontend through chrome. I then invite User A to my workspace via email. User A has registered an account through the invitation link and set a password. User A logs in to the Dify using the account and password set by user A and can use the Chatbot created by user A. I then removed user A from the workspace.

It is believed that user A cannot log in to Dify. However, user A successfully logs in to Dify using the email address and password set previously.. And, he was entering his own workspace, not the one I had set up.
Although he cannot access my workspace, his own workspace is still stored in my volume folder. If he creates a large knowledge base, it will seriously waste my hard disk space, which is not what I want.

✔️ Expected Behavior

User A is deleted from the workspace. User A cannot log in to Dify. so he doesn't waste my hardware and software resources.

❌ Actual Behavior

User A is deleted from the workspace. User A cant log in to Dify. so he can waste my hardware and software resources.

Originally created by @majestichou on GitHub (Apr 17, 2024). Originally assigned to: @GarfieldDai on GitHub. ### Self Checks - [X] This is only for bug report, if you would like to ask a quesion, 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] Pleas do not modify this template :) and fill in all the required fields. ### Dify version 0.6.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I started the Dify service using docker and then accessed the Dify frontend through chrome. I then invite User A to my workspace via email. User A has registered an account through the invitation link and set a password. User A logs in to the Dify using the account and password set by user A and can use the Chatbot created by user A. I then removed user A from the workspace. **It is believed that user A cannot log in to Dify. However, user A successfully logs in to Dify using the email address and password set previously.**. **And, he was entering his own workspace, not the one I had set up. Although he cannot access my workspace, his own workspace is still stored in my volume folder. If he creates a large knowledge base, it will seriously waste my hard disk space, which is not what I want.** ### ✔️ Expected Behavior User A is deleted from the workspace. User A cannot log in to Dify. so he doesn't waste my hardware and software resources. ### ❌ Actual Behavior User A is deleted from the workspace. User A cant log in to Dify. so he can waste my hardware and software resources.
yindo added the 🐞 bug label 2026-02-21 17:43:50 -05:00
yindo closed this issue 2026-02-21 17:43:50 -05:00
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 🐞 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#2279
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?