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

Add App permission control #8450

New Issue
Closed
opened 2026-02-21 18:25:45 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 18:25:45 -05:00
Owner
Copy Link
Copy Source

Originally created by @MrXionGe on GitHub (Feb 20, 2025).

Self Checks

  • 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.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

I hope that every app can configure permissions (me or all team members), just like the permissions of the knowledge base.

Image

When I use Dify with my friends, everyone can view or edit other people's apps.
This is not safe enough.
For example, I created an app and released it to production. I am worried that this app will be edited by others accidentally. Because it will affect the production app.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @MrXionGe on GitHub (Feb 20, 2025). ### Self Checks - [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. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. I hope that every app can configure permissions (me or all team members), just like the permissions of the knowledge base. ![Image](https://github.com/user-attachments/assets/c5188599-3c49-4ed6-b592-36f73a139e42) When I use Dify with my friends, everyone can view or edit other people's apps. This is not safe enough. For example, I created an app and released it to production. I am worried that this app will be edited by others accidentally. Because it will affect the production app. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 18:25:45 -05:00
yindo closed this issue 2026-02-21 18:25:45 -05:00
yindo commented 2026-02-21 18:25:45 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 23, 2025):

Hi, @MrXionGe. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • You requested a feature for app permission controls similar to those for the knowledge base.
  • The current system allows all team members to view or edit apps, risking accidental changes to production apps.
  • Configurable permissions are needed to enhance security and prevent unauthorized modifications.
  • No further comments or developments have been made on this issue.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of Dify by commenting here to keep the discussion open.
  • If there are no updates, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Mar 23, 2025): Hi, @MrXionGe. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary:** - You requested a feature for app permission controls similar to those for the knowledge base. - The current system allows all team members to view or edit apps, risking accidental changes to production apps. - Configurable permissions are needed to enhance security and prevent unauthorized modifications. - No further comments or developments have been made on this issue. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of Dify by commenting here to keep the discussion open. - If there are no updates, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 18:25:46 -05:00
Author
Owner
Copy Link
Copy Source

@igangz commented on GitHub (Apr 1, 2025):

Strongly recommend supporting this feature.

@igangz commented on GitHub (Apr 1, 2025): Strongly recommend supporting this feature.
yindo commented 2026-02-21 18:25:46 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 1, 2025):

@crazywoola, the user has indicated that they strongly recommend supporting the feature for app permission controls. Could you please assist them with this issue?

@dosubot[bot] commented on GitHub (Apr 1, 2025): @crazywoola, the user has indicated that they strongly recommend supporting the feature for app permission controls. Could you please assist them with this issue?
yindo commented 2026-02-21 18:25:46 -05:00
Author
Owner
Copy Link
Copy Source

@laipz8200 commented on GitHub (Apr 28, 2025):

We currently don't have plans to support advanced permission controls. However, if you need this feature, feel free to reach out to us at business@dify.ai. We'd be happy to help!

@laipz8200 commented on GitHub (Apr 28, 2025): We currently don't have plans to support advanced permission controls. However, if you need this feature, feel free to reach out to us at [business@dify.ai](mailto:business@dify.ai). We'd be happy to help!
yindo commented 2026-02-21 18:25:46 -05:00
Author
Owner
Copy Link
Copy Source

@hxt365 commented on GitHub (May 14, 2025):

+1

@hxt365 commented on GitHub (May 14, 2025): +1
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 💪 enhancement
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#8450
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?