fix(plugin-multi-tenant): constrain results to assigned tenants when present #13365
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.
Extension of #13213
This PR correctly filters tenants, users and documents based on the users assigned tenants if any are set. If a user is assigned tenants then list results should only show documents with those tenants (when selector is not set). Previously you could construct access results that allows them to see them, but in the confines of the admin panel they should not see them. If you wanted a user to be able to see a "public" tenant while inside the admin panel they either need to be added to the tenant or have no tenants at all.
Note that this is for filtering only, access control still controls what documents a user has access to a document. The filters are and always have been a way to filter out results in the list view.