Default settings and permission settings on package
Question
How do the default and permission settings work on package?
Answer
The permission settings on package are shown in the table below:
| Parent | Default | Group | Personal | Result |
| no | - | - | - | no |
| no | no | - | - | no |
| no | yes | - | - | yes |
| no | x | - | no | no |
| no | x | - | yes | yes |
| no | x | no | - | no |
| no | x | yes | - | yes |
| no | x | no | no | no |
| no | x | no | yes | yes |
| no | x | yes | no (not possible)** | yes |
| no | x | yes | yes | yes |
| yes | - | - | - | yes |
| yes | no | - | - | no |
| yes | yes | - | - | yes |
| yes | x | - | no | no |
| yes | x | - | yes | yes |
| yes | x | no | - | no |
| yes | x | yes | - | yes |
| yes | x | no | no | no |
| yes | x | no | yes (not possible)** | no |
| yes | x | yes | no | no |
| yes | x | yes | yes | yes |
* If you set permissions on a group, the settings are automatically checked on the user who is a member of the group.
- not specified
x value does not matter
The default setting is inherited from the parent package.
If there is no default setting at all (only for newly created Roots), the repository is not visible by default, or reading is not allowed.
Admin has access to all packages, regardless of the settings.
The evaluation of rights on a child package does not take into account how the rights were evaluated on the parent package; only the result of the evaluation on the parent (no/yes) enters into the decision.
Further recommended information about permissions: Permissions in case a user is a member of two groups with different settings.