Skip to main content

Permissions

The access to every resource in MINEO is controlled by a fine-grained permission system which allows to control who can view and edit them for each user and group. The project's users and groups can be managed the project page. Resources public access can be configured also from this page.

The permissions dialog has two parts: the Public access panel, which sets resource-wide visibility, and the Permissions table, which assigns explicit per-user or per-group access.

Public access panel​

The public access panel allows you to share your notebook with anyone registered in MINEO, even if they are not members of the project.

info

To access public resources, users must be logged in MINEO previously.

Users with full permissions over a resource can define public access over it. The options are:

  • Restricted: Only explicitly assigned users will have access to the notebook.
  • Reading: Anyone will be able to read the notebook, but not to edit it unless explicitly allowed.
  • Writing: Anyone will be able to read and edit the notebook.
info

Notebooks with Reading and Writing permissions can be accessed using URL directly. In notebook docs is explained how to share a notebook.

Permissions table​

If you want to explicitly assign permissions to users, you will do it in this table. You can control permissions for every particular member of your project, or cluster them together in groups to control their permissions in bulk. You can switch between user and group mode in the switch in the top right corner of the table.

info

Extended explanation about project users and groups can be found in Projects module.

Permission table columns are explained below:

  • Username: Name of the user/group.
  • Object Permissions: View: Whether to allow or forbid the user/group to view the notebook. You can also choose to inherit the permission from the parent node.
  • Object Permissions: Edit: Whether to allow or forbid the user/group to edit the notebook. You can also choose to inherit the permission from the parent node.
  • Calculated Permissions: View: Whether the user/group will be able to view the notebook.
  • Calculated Permissions: Edit: Whether the user/group will be able to edit the notebook.
info

Final calculated permissions take multiple things into consideration to generate the final permission for each user. If user belongs to a group, and Inherit permission is selected, user will inherit group permissions over the resource. If user does not belong to any group, Inherit permission will take into account permissions over parent element in file system.