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

[Data segregation / Admin organization] Administration buggy if right "manage marking" #5980

Closed
Lhorus6 opened this issue Feb 15, 2024 · 0 comments · Fixed by #5992
Closed
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@Lhorus6
Copy link

Lhorus6 commented Feb 15, 2024

Description

If a user who is an organization administrator has "manage marking" capabilities, the right-hand menu in the control panel is buggy (see screenshot).

Environment

OCTI 5.12.31

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Put Org A as platform main org
  2. Create User B in Org B
  3. Put User B as Org admin of Org B
  4. Give to User B the capability "manage markings"
  5. Log in with User B
  6. Go to Settings > Security

Expected Output

Screenshot 2024-02-15 123849

Actual Output

Screenshot 2024-02-15 124038

@Lhorus6 Lhorus6 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 15, 2024
@Lhorus6 Lhorus6 changed the title [Data segregation / Admin organization] Administration buggy if right "manage marking". [Data segregation / Admin organization] Administration buggy if right "manage marking" Feb 15, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.0 milestone Feb 15, 2024
@nino-filigran nino-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Feb 15, 2024
@Kedae Kedae self-assigned this Feb 15, 2024
@Kedae Kedae added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected 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.

4 participants