I noticed the following when creating new Spaces in the Inventory from the ELN-LIMS UI as an instance admin (single-group instance, openBIS v20.10.5):
- When creating a new Space and checking the “Read-only” option, it is not possible to delete the Space from the ELN-LIMS UI (even as an instance admin). However, deletion is possible from the old Admin UI. Is this intentional or a bug? What is the intention behind the “Read-only” option - to create a Space with Observer rights to anyone but the instance admin?
- There is a typo in the description of the “Read-only” checkbox:
Indicates if writing the she space should be disabled for non admin users.
What is the intention behind the “Read-only” option - to create a Space with Observer rights to anyone but the instance admin?
Normally, the intention behind the “Read-only” option when creating a new Space in the Inventory is to allow users with Observer permissions to access and view the contents of the Space without being able to modify or edit them. By selecting the “Read-only” option, the Space is created with restricted permissions that prevent anyone other than the instance admin from making changes to the Space, ensuring that the contents of the Space remain secure and unaltered.
This feature can be particularly useful in situations where sensitive data is being stored within a Space and needs to be kept secure, while still allowing certain users to access and view the data for informational purposes. By creating a “Read-only” Space, instance admins can control access to the data while still allowing Observer users to view the contents of the Space.