8000 DEFAULT_ORGANIZATION_ID no longer working as expected · Issue #4788 · formbricks/formbricks · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

DEFAULT_ORGANIZATION_ID no longer working as expected #4788

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
jonas-hoebenreich opened this issue Feb 21, 2025 · 6 comments · Fixed by #5046
Closed

DEFAULT_ORGANIZATION_ID no longer working as expected #4788

jonas-hoebenreich opened this issue Feb 21, 2025 · 6 comments · Fixed by #5046
Assignees
@gupta-piyush19

Comments

@jonas-hoebenreich
Copy link
Contributor

Issue Summary

We've been using DEFAULT_ORGANIZATION_ID and DEFAULT_ORGANIZATION_ROLE to automatically assign new users to our organization on their first login, granting them member rights. However, after the introduction of product-based access controls, this no longer works as expected.

Instead of having viewer access to the surveys, users now receive the following error message upon sign-up: "Your account doesn’t have access to any products yet."

Expected Behavior

New users should be automatically assigned to the specified organization and granted viewer access upon their first login. Maybe we could add a variable like DEFAULT_TEAM_ID to automatically add them also to a specific team granting them certain access rights.

Other information (incl. screenshots, Formbricks version, steps to reproduce,...)

No response

Your Environment

Self-hosted Formbricks
@mattinannt
Copy link
Member
mattinannt commented Mar 18, 2025 •
edited
Loading

@jonas-hoebenreich Sorry, this issue got lost during a larger internal restructuring. We will focus on this issue asap.

@gupta-piyush19 Could you please reproduce the issue and propose a fix? I think Jonas' suggestion of adding a DEFAULT_TEAM_ID could be a good approach.

@gupta-piyush19
Copy link
Contributor

Yeah, that sounds good!
I'll push this fix today.

@jonas-hoebenreich
Copy link
Contributor Author

thank you 🙏

@gupta-piyush19
Copy link
Contributor

Hi, @jonas-hoebenreich ! We already support inviting users with teamIds. Do you think this will solve your issue?
Or would you like to assign the users to a team when they first log in? It isn't easy to detect the first login of the users.

@gupta-piyush19 gupta-piyush19 mentioned this issue Mar 24, 2025
Merged
12 tasks
@jonas-hoebenreich
Copy link
Contributor Author

Hi @gupta-piyush19, thanks for looking into this. We're not inviting users but instead we're using Azure user groups as single source of truth to decide who is allowed to access the application. So when a new employee logs in for the first time the user is automatically created inside Formbricks and should be assigned to the team DEFAULT_TEAM_ID.

@gupta-piyush19
Copy link
Contributor

Got it.
I've raised a PR to implement this fix. I made the assumption that the DEFAULT_TEAM_ID will be present in the DEFAULT_ORGANIZATION_ID , so please ensure that you have the same setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gupta-piyush19 gupta-piyush19

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: adds support for default_team_id env var formbricks/formbricks
3 participants
@mattinannt @gupta-piyush19 @jonas-hoebenreich
0