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.
Summary
This PR introduces the concept of security levels, enhancing the control over which AI models can be utilized within different Spaces based on their security requirements. Security levels are defined by a name, description, and a numeric value that dictates access permissions. This feature allows administrators to assign security levels to both models and Spaces, ensuring that only models meeting the required security criteria are accessible within a given Space.
Notes
frontend/pnpm-lock.yaml
by using'
instead of"
, also some packages are removed (widgets for example). This PR does not add/change any dependencies so the updated file is not included in this PR.frontend/packages/intric-js/src/types/schema.d.ts
does not seem to be up-to-date. We get a bigger diff than expected that contains unrelated changes. Not sure how this is supposed to be managed, but we have manually changed thefrontend/packages/intric-js/update.js
to use the local backend when regenerating.Screenshots
List security levels
Create/edit security level
Space security level admin
Change space security level message