You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A member of a "read-only" group where Microscope.json files are kept to be made available to all users of a facility or a lab, is able to see the read-only group in the "Save in group:" list and is able to successfully save in the group.
Expected behavior
Desired behavior is that members of a "read-only" group where Microscope.json files are kept to be made available to all users of a facility or a lab, should not be able to have write access to the group to avoid over-writing and messing up a given microscope configuration.
To Reproduce
Steps to reproduce the behavior:
Created "UMMS_PMM_BIG_Microscopy" as a "Read-Only" group
Created "Microscope_User_Test_Group1" as a full-fledged "Read-Write" group.
Created "Microscope User1" as a member of both UMMS_PMM_BIG_Microscopy and Microscope_User_Test_Group1 (NOT OWNER).
Logged in as Microscope_User1
Launch Manage Instrument in MMA
Both groups are available as "Load from group" and "Save in group"
Microscope.json file can apparently be saved in read-only group
The text was updated successfully, but these errors were encountered:
strambc
changed the title
STRAMBIO:
STRAMBIO: Member of "read-only" group can save Microscope.json file in it
Nov 12, 2022
strambc
changed the title
STRAMBIO: Member of "read-only" group can save Microscope.json file in it
STRAMBIO: Member of "read-only" group can see it in "Save in group" list and can "save Microscope.json file in it
Nov 12, 2022
strambc
changed the title
STRAMBIO: Member of "read-only" group can see it in "Save in group" list and can "save Microscope.json file in it
STRAMBIO: Member of "read-only" group can see it in "Save in group" list and can "Save" Microscope.json file
Nov 12, 2022
Note: it is saved in "read-only" group but it is saved under Microscope_User1 MMA_Microscopes. Does not appear to interfere with shared microscopes. But it is very confusing.
Describe the bug
A member of a "read-only" group where Microscope.json files are kept to be made available to all users of a facility or a lab, is able to see the read-only group in the "Save in group:" list and is able to successfully save in the group.
Expected behavior
Desired behavior is that members of a "read-only" group where Microscope.json files are kept to be made available to all users of a facility or a lab, should not be able to have write access to the group to avoid over-writing and messing up a given microscope configuration.
To Reproduce
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: