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

Optional All Objects for Tenancy Manager #461

Open
2 tasks
jon-nfc opened this issue Jan 2, 2025 · 0 comments
Open
2 tasks

Optional All Objects for Tenancy Manager #461

jon-nfc opened this issue Jan 2, 2025 · 0 comments

Comments

@jon-nfc
Copy link
Member

jon-nfc commented Jan 2, 2025

Currently the Tenancy manager that is in use, filters the objects to those that are within the organization(s) the user has view access to. This is intentional so as to enable multi-tenancy.

Details

The tenancy manager requires an option that can be passed as an attribute, that allows ALL items to be returned, regardless of the users organization.

This is required so that if an authenticated user tries to edit an item in a different organization the correct return can be created (normally HTTP/403). In addition, there are models that have database constraints (uniqueness) and this requires access to ALL items within the table so that validation can occur.

Without this option, any query made by a user will return items only for their organizations which has the potential to create errors that could be avoided (unique table constraint, etc.).

Note: By default the queryset should always return filtered to user orgs results

Links

  • 0b362f0 Test case that can't be run due to this feature missing.

Requirements

  • Can query to fetch ALL table items
  • By default, the returned queryset is filtered.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

1 participant