On this page


Modify package permissions

To modify the permissions of the package

  1. Right-click the package or its shape and select Permissions. The Permissions of Package dialog opens.

    The full name of the dialog depends on the selected package name. Thus, if you select to modify the permissions of the package domain, the Permissions of Package domain dialog opens.

  2. Change global permissions appropriately:

    • To restrict editing of the selected package leaving the rest of the model editable, select Read-Write as Global permission.
    • To restrict editing of the entire model leaving only the selected package editable, select Read-Only as Global permission.

  3. Add a new package permission:

    1. Click the Add button under the Package permissions table. The Select User/Group dialog opens.

    2. Use search bar to filter users or groups, then click to select the check box near the user or group name.



    3. Click OK and see the new row appeared in the Package permissions table.
    4. Click the Permission cell and select:

      • Read-Only to restrict editing of the package for the selected user/group.
      • Read-Write to allow editing of the package for the selected user/group.

    5. If you don't want to apply the same permission on the subpackages of this package, click the Apply To cell and select This package only.

  4. Add as many permissions as you need by repeating step 3.
  5. Close the Permissions of Package dialog.

Permission conflict logic

  1. 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-Write permission.
  2. User is granted different permissions through the Users and Groups tabs, if permissions are different, User permission wins.
  3. 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.
  4. 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.

Inheritable permissions

The Permissions of Package dialog includes a few options for handling inheritable permissions. The following table provides their descriptions.

OptionDescription

Include inheritable permissions from the parent

Inheritable permissions of the package are those that apply to its subpackages as well.

By default, these permissions are displayed together with individual permissions of every subpackage, but cannot be modified or deleted there. If you want to hide them, click to clear the check box.

Let's say you have a package Model and a subpackage Requirements.

If you set on the package Model the Read-Only permission for certain user and leave the default setting to apply this permission on subpackages as well, the Permissions of Package domain dialog also displays the permission, if the relevant check box is selected. The Inherited From cell value of the inherited permission is Model.

Showing inheritable permissions of the parent package

Replace all subpackages permissions with inheritable permissions from this package

Inheritable permissions of the package are those that apply to its subpackages as well.

If the package, whose permissions you modify, has subpackages, you can choose to replace their individual permissions with those of the parent package. Make sure the appropriate permissions are set as inheritable and click to select the check box.