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

Add Confidence level on Users #4304

Closed
Jipegien opened this issue Sep 11, 2023 · 1 comment · Fixed by #5436
Closed

Add Confidence level on Users #4304

Jipegien opened this issue Sep 11, 2023 · 1 comment · Fixed by #5436
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@Jipegien
Copy link
Member

Jipegien commented Sep 11, 2023

Use case

Users have a Max Confidence level that will be used when creating Knowledge.
As connectors, stream and feeds used a user to upsert data, confidence level in their config is no longer needed. They will use the max confidence level of the users they are associated with.

In User's edition form, a dedicated panel allows to set the max confidence level

No migration

We do not know what is the value used in the connectors configuration files of our users, and we cannot know which user is used for a connector, thus we cannot magically migrate the existing users with a smart max confidence value.
For instance, migrating users to 100 would be a very dangerous move as connectors would suddenly be able to overwrite all data in the platform.

For this reason, no migration will be executed. Platform admins are expected to configure their confidence policy throughout their platform.

Subtasks:

  • Managing a “max confidence level” for a user
  • Enforce specific rights to manage confidence levels of users (capability SETACCESS)
  • [Product] Anticipate the breaking change using Filigran's communication tools

Linked to issues

Next steps

  • Using max confidence level of the associated user when upserting data
  • Taking into account the max confidence level of users when they try to modify the confidence level of an Object

Further comments

Note this feature will then be leveraged for #2517 in the future.

@Jipegien Jipegien added the feature use for describing a new feature to develop label Sep 11, 2023
@Jipegien Jipegien added this to the Release 5.13.0 milestone Sep 11, 2023
@Jipegien Jipegien changed the title Add Confidence level on livre stream and feeds Add Confidence level on Users and stream/feeds/connectors Oct 2, 2023
@SamuelHassine
Copy link
Member

Also implement the option "validate_before_import".

@SamuelHassine SamuelHassine modified the milestones: Release 5.13.0, Release 6.0.0 Jan 16, 2024
labo-flg added a commit that referenced this issue Jan 24, 2024
Co-authored-by: Sarah Bocognano <98532359+SarahBocognano@users.noreply.github.com>
@labo-flg labo-flg changed the title Add Confidence level on Users and stream/feeds/connectors Add Confidence level on Users and Groups Jan 25, 2024
labo-flg added a commit that referenced this issue Jan 25, 2024
Co-authored-by: BocognanoSarah <sarah.bocognano@filigran.io>
labo-flg added a commit that referenced this issue Jan 25, 2024
Co-authored-by: Sarah Bocognano <98532359+SarahBocognano@users.noreply.github.com>
labo-flg added a commit that referenced this issue Jan 25, 2024
Co-authored-by: BocognanoSarah <sarah.bocognano@filigran.io>
@labo-flg labo-flg changed the title Add Confidence level on Users and Groups Add Confidence level on Users Jan 25, 2024
labo-flg added a commit that referenced this issue Jan 29, 2024
Co-authored-by: Sarah Bocognano <98532359+SarahBocognano@users.noreply.github.com>
labo-flg added a commit that referenced this issue Jan 29, 2024
Co-authored-by: BocognanoSarah <sarah.bocognano@filigran.io>
Kedae pushed a commit that referenced this issue Jan 29, 2024
Co-authored-by: Sarah Bocognano <98532359+SarahBocognano@users.noreply.github.com>
Co-authored-by: BocognanoSarah <sarah.bocognano@filigran.io>
@Kedae Kedae added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants