Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[P1] Keep the team gate at the Actual-specific boundary
This teams entry is on the only GitHub connector, so it affects every Dex client, not just Actual Budget. Current main registers oauth2-proxy, Headlamp, Vault, KSail, Crossview, and kubectl on this connector; docs/oidc-kubectl.md explicitly permits any devantler-tech organization member, and the current Crossview configuration intentionally treats any organization member as its effective gate. Merging this therefore silently revokes those documented access paths for every non-maintainers member. Enforce the restriction at an Actual-specific boundary, such as a dedicated client or proxy with an app-scoped gate, and add positive and negative authentication coverage proving the other Dex consumers retain their current organization-member policy.