By default, all packages in the project can be reviewed and modified by any Teamwork Cloud user.
There are two levels of permissions:
The Global permission specifies which permission is applied for all project packages for all users:
Select Read-Write as the the Global permissionto restrict to allow editing of the selected package, leaving the rest of the model editableentire model.
Select Read-Only as the the Global permission to restrict to restrict editing of the entire model, leaving only the selected package editable.
For each package, the global permission can be over-specified by the package permission
.
Note
Global permissions can be overridden by package permissions:
Read-Only global permission can be overridden by a package with Read-Write permission. This allows the user/group to edit the package, whereas editing the rest of the model is restricted.
Read-Write global permission can be overridden by a package with Read-Only permission. This restricts the user/group from editing the package, whereas editing the rest of the model is allowed.
Package permissions specify the permissions applied to a particular package for a particular user. If no permission is specified for the package, the global permission is valid.
If you want to restrict editing of a package for a specific user or user group, you can easily do this by modifying the package permissions. You can modify package permissions if you have the Manage model permissions permission on that project. Select:
Read-Only to restrict editing of the package for the selected user.
Read-Write to allow editing of the package for the selected user.
By default, Read-Write as the Global permission is assigned to the project and the Read-Only permission is assigned to the package.
Note
title
Project-level and package-level permissions
The TWCloud project-level Read-WritePermissions can be overridden by package permissions. For example, if a user was granted project-level Read-Write permissions, but was assigned Read-Only permissions for a particular package, that user will not be allowed to make changes to the elements owned by the package and the package itself.
If a user has project-level Read-Only permissions, package permissions cannot override them.
Permissions conflict logic
There are some cases when permissions for users or user group might be conflicting, these cases and the final outcome are described below:
If the user belongs to two groups and one group is granted Read-Only permission, while another group - Read-Write permission. In this permission conflict, the user will be granted with higher permission, which is Read-Writepermission.
User is granted different permissions through the Users and Groups tabs, if permissions are different, User permission wins.
If permission is granted simultaneously for both users and groups, then this permission will be granted for standalone users and for users within the selected groups.
In case of nested packages with each having different permissions (Read-Only/Read-Write), owned element modification mode is decided from the closest root package permissions in the tree.