Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
rdms:data:permissions [2023/05/04 09:51] jelte |
rdms:data:permissions [2023/05/11 16:48] (current) jelte Included table |
====== Permissions and Inheritance====== | ====== Permissions and Inheritance====== |
| |
Within the RDMS, there are four levels of **permissions** or user privileges to files and folders. | Within the RDMS, there are **four levels of permissions** or user privileges to files and folders that can be defined by the users. |
| |
**Own**: The user owns the data object (file) or the collection (folder) and has the full permission on reading, modifying, and sharing the object. | In an order of ascending privileges, these permissions are 'Null', 'Read', 'Read/Write' and 'Own'. |
| |
**Write**: The user has read and write access to the object. | Please see the following table for a summary of what these different permissions allow within the RDMS: |
| |
**Read**: The user can only read the object or its content. This also allows to make a (editable) copy of the file/folder. | ^ Permission Level ^ Read ^ Modify ^ Create New ^ Delete ^ Share ^ |
| | **Null** | {{:rdms:data:1280px-eo_circle_red_blank.svg.png?20|}} | {{:rdms:data:1280px-eo_circle_red_blank.svg.png?20|}} | {{:rdms:data:1280px-eo_circle_red_blank.svg.png?20|}} | {{:rdms:data:1280px-eo_circle_red_blank.svg.png?20|}} | {{:rdms:data:1280px-eo_circle_red_blank.svg.png?20|}} | |
| | **Read** | {{:rdms:data:eo_circle_green_checkmark.svg.png?20|}} | {{:rdms:data:1280px-eo_circle_red_blank.svg.png?20|}} | {{:rdms:data:1280px-eo_circle_red_blank.svg.png?20|}} | {{:rdms:data:1280px-eo_circle_red_blank.svg.png?20|}} | {{:rdms:data:1280px-eo_circle_red_blank.svg.png?20|}} | |
| | **Write** | {{:rdms:data:eo_circle_green_checkmark.svg.png?20|}} | {{:rdms:data:eo_circle_green_checkmark.svg.png?20|}} | {{:rdms:data:eo_circle_green_checkmark.svg.png?20|}} | {{:rdms:data:1280px-eo_circle_red_blank.svg.png?20|}} | {{:rdms:data:1280px-eo_circle_red_blank.svg.png?20|}} | |
| | **Own** | {{:rdms:data:eo_circle_green_checkmark.svg.png?20|}} | {{:rdms:data:eo_circle_green_checkmark.svg.png?20|}} | {{:rdms:data:eo_circle_green_checkmark.svg.png?20|}} | {{:rdms:data:eo_circle_green_checkmark.svg.png?20|}} | {{:rdms:data:eo_circle_green_checkmark.svg.png?20|}} | |
| |
**None**: The user does not have any permission on the object. One can use 'none' when removing the previously assigned permissions to a user. When you are the owner of an object and accidentally set your own permissions to 'none', you will internally still remain the owner and you can recover your privileges by again assigning another permission level. | |
| |
**Additional Notes for RDMS Team Drives and user permissions** | And for a more detailed explanation of what this permissions mean: |
| |
| **Own**: The user owns the data object (file) or the collection (folder) and has the full permission on reading, modifying (including deletion), and sharing. |
| |
| **Write**: The user has read and write access to the object. |
| |
| **Read**: The user can only read the object or its content. This also allows to make a (editable) copy of the file/folder. |
| |
Within the Team Drive space, the 'read' and 'write' permissions behave slightly differently: | **Null**: The user does not have any permission on the object. One can use 'none' when removing the previously assigned permissions to a user. When you are the owner of an object and accidentally set your own permissions to 'none', you will internally still remain the owner and you can recover your privileges by again assigning another permission level. |
| |
- In a RDMS Team Drive, users with 'read' permissions **cannot downloads/copy a file/folder**. Instead 'write' permissions are needed in this case. | **Important Note** |
| |
- In a RDMS Team Drive, users with 'write' permissions **cannot delete files/folder** with this permission level. Within this section of the RDMS, the owner has to delete files/folders. | * While 'write' permissions allow to create new objects and modify existing ones, it does not allow for the deletion of objects |
| |
===== Inheritance ===== | ===== Inheritance ===== |