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

Read-Only Role for Exploring Created Apps #7930

New Issue
Open
opened 2026-02-21 18:23:06 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 18:23:06 -05:00
Owner
Copy Link
Copy Source

Originally created by @tsuda-haruni on GitHub (Jan 30, 2025).

Originally assigned to: @crazywoola on GitHub.

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.

Description

Currently, Dify provides a standard role that allows members to view applications, but there is no role that restricts access to only the apps created through the "Explore" feature while hiding the Studio and Tools tabs.

Expected Behavior

  • A new "Read-Only Explorer" role should be added.
  • Users assigned to this role should only see the applications they created via Explore.
  • Studio and Tools tabs should be hidden for these users.
  • This role should prevent access to editing or managing applications but allow viewing and interacting with them.

Why This is Important

  • Enhances security by limiting access to unnecessary settings.
  • Simplifies app deployment for businesses that want to provide limited access to specific users.
  • Prevents accidental modifications by restricting access to critical configurations.
  • Facilitates corporate use cases, making Dify more viable for business adoption.

Would love to see this feature added as it would greatly improve usability for organizations managing multiple users!

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 @tsuda-haruni on GitHub (Jan 30, 2025). Originally assigned to: @crazywoola on GitHub. ### 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. ### **Description** Currently, Dify provides a standard role that allows members to view applications, but there is no role that restricts access to only the apps created through the "Explore" feature while hiding the **Studio** and **Tools** tabs. ### **Expected Behavior** - A new **"Read-Only Explorer"** role should be added. - Users assigned to this role should **only see** the applications they created via **Explore**. - **Studio and Tools tabs should be hidden** for these users. - This role should prevent access to editing or managing applications but allow viewing and interacting with them. ### **Why This is Important** - **Enhances security** by limiting access to unnecessary settings. - **Simplifies app deployment** for businesses that want to provide limited access to specific users. - **Prevents accidental modifications** by restricting access to critical configurations. - **Facilitates corporate use cases**, making Dify more viable for business adoption. Would love to see this feature added as it would greatly improve usability for organizations managing multiple users! ### 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:23:06 -05:00
yindo commented 2026-02-21 18:23:06 -05:00
Author
Owner
Copy Link
Copy Source

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

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

Issue Summary

  • Proposal for a "Read-Only Explorer" role in Dify.
  • This role would limit users to viewing only their created applications via the "Explore" feature.
  • Aims to enhance security and support corporate use cases by restricting access.
  • No further comments or developments have been made on this issue.

Next Steps

  • Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here.
  • If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Mar 2, 2025): Hi, @tsuda-haruni. 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** - Proposal for a "Read-Only Explorer" role in Dify. - This role would limit users to viewing only their created applications via the "Explore" feature. - Aims to enhance security and support corporate use cases by restricting access. - No further comments or developments have been made on this issue. **Next Steps** - Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here. - If there is no further activity, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 18:23:06 -05:00
Author
Owner
Copy Link
Copy Source

@tsuda-haruni commented on GitHub (Mar 2, 2025):

Hi.

Thanks for following up on this issue.
I still have this requirement and believe the "Read-Only Explorer" role would be valuable for enhancing security and supporting corporate use cases.

I'd appreciate it if the team could keep this issue open for future consideration.

Thank you!

@tsuda-haruni commented on GitHub (Mar 2, 2025): Hi. Thanks for following up on this issue. I still have this requirement and believe the "Read-Only Explorer" role would be valuable for enhancing security and supporting corporate use cases. I'd appreciate it if the team could keep this issue open for future consideration. Thank you!
yindo commented 2026-02-21 18:23:06 -05:00
Author
Owner
Copy Link
Copy Source

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

@takatost, the user @tsuda-haruni has confirmed that the proposal for a "Read-Only Explorer" role is still relevant and valuable for enhancing security and supporting corporate use cases. Could you please assist them with this issue? Thank you!

@dosubot[bot] commented on GitHub (Mar 2, 2025): @takatost, the user @tsuda-haruni has confirmed that the proposal for a "Read-Only Explorer" role is still relevant and valuable for enhancing security and supporting corporate use cases. Could you please assist them with this issue? Thank you!
yindo commented 2026-02-21 18:23:06 -05:00
Author
Owner
Copy Link
Copy Source

@tsuda-haruni commented on GitHub (Feb 3, 2026):

open

@tsuda-haruni commented on GitHub (Feb 3, 2026): open
yindo commented 2026-02-21 18:23:06 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 3, 2026):

@crazywoola The user tsuda-haruni has indicated that the issue is still relevant and should be reopened despite being marked stale and closed. Could you please assist with this?

@dosubot[bot] commented on GitHub (Feb 3, 2026): @crazywoola The user tsuda-haruni has indicated that the issue is still relevant and should be reopened despite being marked stale and closed. Could you please assist with this?
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#7930
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?