Repository navigation
feat: system user relations and policy-managed application access - #4
Merged
Merged
Conversation
Yniphe
marked this pull request as ready for review
October 7, 2026 13:32
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Ordinary collections can now reference a system user, for example a department's manager, using an M2O field with the
@userstarget. The picker, saved values, table labels and filters use a bounded user directory. Native UUID foreign keys support RESTRICT or SET NULL; directory access and new assignments require permission to read users. Existing references remain editable when their user is disabled, without granting access to system tables.OAuth applications can opt into policy-managed access. Policies grant application login and service permissions; tokens contain only currently effective permissions approved by the user. Permission changes require fresh consent, and permissions added after approval cannot broaden a pending authorization. Existing applications retain their current access behavior until the mode is enabled.
The change includes guarded migrations, API documentation, Russian/English UI copy and integration tests for authorization, FK behavior, filters, token claims, consent and revocation. User-defined fields are not created automatically.
Validation:
pnpm check,pnpm buildandpnpm packages:checkpassed locally and in CI. The full Core suite passed 492 tests and UI passed 143; the opt-in live LavinMQ, performance and disposable visual suites were skipped. The focused OAuth suite passed again after migration rollback hardening. Visual browser verification was not completed. CI passed the split Core/UI startup, authenticated API, credential isolation, restart and graceful stop checks, plus Helm lint and routing validation.