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

Auto-join newly registered accounts to the default workspace #22221

New Issue
Open
opened 2026-02-21 20:16:12 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:16:12 -05:00
Owner
Copy Link
Copy Source

Originally created by @lin-snow on GitHub (Feb 13, 2026).

Originally assigned to: @lin-snow on GitHub.

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 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.

In our Enterprise deployment, we want newly registered users to be automatically added to a company-wide “default workspace” for onboarding and centralized access management.

Today, after a user signs up via SSO/OAuth (or other registration flows), they become the owner of their own workspace, but they are not automatically included in the enterprise default workspace. This creates friction:

  • Admins need to manually add users to the default workspace after every registration.
  • Users may miss shared resources and policies that are only available in the default workspace.
  • It is harder to enforce enterprise onboarding and permissions consistently.

We already have an Enterprise service that can ensure membership in the default workspace (idempotent), but Dify currently does not call it during registration.

2. Additional context or comments

Enterprise provides an Inner API

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @lin-snow on GitHub (Feb 13, 2026). Originally assigned to: @lin-snow on GitHub. ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [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. In our Enterprise deployment, we want newly registered users to be automatically added to a company-wide “default workspace” for onboarding and centralized access management. Today, after a user signs up via SSO/OAuth (or other registration flows), they become the owner of their own workspace, but they are not automatically included in the enterprise default workspace. This creates friction: - Admins need to manually add users to the default workspace after every registration. - Users may miss shared resources and policies that are only available in the default workspace. - It is harder to enforce enterprise onboarding and permissions consistently. We already have an Enterprise service that can ensure membership in the default workspace (idempotent), but Dify currently does not call it during registration. ### 2. Additional context or comments Enterprise provides an Inner API ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 20:16:12 -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 💪 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#22221
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?