-
-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[feature] Organization-independent firmware categories #204
Labels
enhancement
New feature or request
Comments
The problem right now is that if I am not mistaken the organization information is only on the category and most of the other objects rely on that for multi-tenancy, so this can be done but would require changing a few parts of the code. |
pandafy
added a commit
that referenced
this issue
Feb 20, 2025
4 tasks
pandafy
added a commit
that referenced
this issue
Feb 20, 2025
pandafy
added a commit
that referenced
this issue
Feb 20, 2025
pandafy
added a commit
that referenced
this issue
Feb 21, 2025
pandafy
added a commit
that referenced
this issue
Mar 3, 2025
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Similar to configuration templates, it should be possible to create a firmware category without assigning it to a organization so that it can be used by several organizations.
The text was updated successfully, but these errors were encountered: