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

Management panel for Access Restriction on Knowledge Entities #4961

Open
Jipegien opened this issue Nov 23, 2023 · 0 comments
Open

Management panel for Access Restriction on Knowledge Entities #4961

Jipegien opened this issue Nov 23, 2023 · 0 comments
Assignees
Labels
feature use for describing a new feature to develop
Milestone

Comments

@Jipegien
Copy link
Member

Use case

With the ability to design Access Restriction on specific Knowledge entities (#3181) comes the risk that some, with time, will be forgotten, creating a Data debt.

Bu having access to a dedicated management panel, administrators will be able to retrieve any restricted Knowledge Entity and "free" it or change those who can access it.

@Jipegien Jipegien added feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team and removed needs triage use to identify issue needing triage from Filigran Product team labels Nov 23, 2023
@Jipegien Jipegien added this to the Release 5.14.0 milestone Nov 23, 2023
@Jipegien Jipegien modified the milestones: Release 5.14.0, Release 5.13.0 Dec 5, 2023
@SamuelHassine SamuelHassine modified the milestones: Release 5.13.0, Release 6.0.0 Jan 16, 2024
@nino-filigran nino-filigran modified the milestones: Release 6.0.0, Short-term candidates Jan 23, 2024
@Jipegien Jipegien modified the milestones: Short-term candidates, Release 6.2.0 Mar 12, 2024
@Jipegien Jipegien modified the milestones: Release 6.2.0, Release 6.4.0 Mar 26, 2024
@Jipegien Jipegien modified the milestones: Release 6.4.0, Release 6.5.0 Apr 17, 2024
@SamuelHassine SamuelHassine added filigran team use to identify PR from the Filigran team and removed filigran team use to identify PR from the Filigran team labels Apr 20, 2024
@nino-filigran nino-filigran self-assigned this Sep 16, 2024
CelineSebe added a commit that referenced this issue Jan 6, 2025
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
Projects
None yet
Development

No branches or pull requests

6 participants