Skip to content
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.

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

[permission] (fix ) use SettingsPermissions and not SettingsFeatures #10398

Merged
merged 1 commit into from
Feb 21, 2025

Conversation

ijreilly
Copy link
Collaborator

oops

@ijreilly ijreilly enabled auto-merge (squash) February 21, 2025 16:28
@Weiko Weiko disabled auto-merge February 21, 2025 16:28
@Weiko Weiko merged commit 1ed9de2 into main Feb 21, 2025
27 checks passed
@Weiko Weiko deleted the perm-oops branch February 21, 2025 16:29
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary

This PR fixes a critical permission control issue by replacing SettingsFeatures with SettingsPermissions in the workspace invitation resolver, ensuring proper access control for workspace user management.

  • Updated guard in /packages/twenty-server/src/engine/core-modules/workspace-invitation/workspace-invitation.resolver.ts to use SettingsPermissions.WORKSPACE_USERS for correct permission checking
  • Ensures workspace invitation management is properly gated behind user permission checks rather than feature flags

1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants