Now you can view the permissions and group members

If you have access to the object card (Read Meta), you can view its permissions. For example, you can track users with write access to the object.

• Object bage > Permissions...

If you want to know the group members, move the cursor over the group.

You see what the Permissions mean

Move the cursor over the radio Button, and the program will tell you more about the permissions.

View users who have a certain permission

Move the cursor over the Permission, and the program will list the users with that Permission.

Other Permissions lists the permissions of the owner and the creator

Now the owner's and the creator's permissions can be found under Other Permissions.

• By default, the document creator gets Write permissions to the document they have added (as before).
• Others have no permissions to it unless the Permission Rules provide them.
• The person you set as the owner gets Write permissions for the object.

Just remember that only a user with the Admin permission to an object can add new groups for Permission Table or change existing Permissions.

You know that the owner can change the ownership of the object to someone else, removing the owner's permissions from himself.

The Connection permission has been removed. Selection with radio button.

Previously, in the Permission table there was a connect Permission. Now this permission has been removed from the table.

• If the user has a Read permission now, he has the opportunity to connect also.
• Now the maximum permissions are set with a Radio Button and not with a Check Box.
• Below is the new and old Permission Table.
  

Inheritance permissions are only visible if no legal rules are applied

This clarifies the interpretation of the table of permissions.

In the picture below, the Permission Rules have been replaced with Modified Rules:

• Permissions have been inherited from the item structure or project.
• Permissions have been allocated to new groups.

You can let other related objects inherit hierarchical rights

Previously, you may have let drawings, models and documents inherit hierarchical rights. Other document types are now included, such as Vertex-compressed (.vxz) files or e-mails.

• This is only visible and available when using hierarchical rights.

The administrator can control which other types this affects.

Add hierarchical permission to a project

In previous versions, it has been possible to add hierarchical permissions to the item structure. Now hierarchical permissions can be added to projects.

• When you give hierarchical permissions to a project, the documents under the project inherit these permissions, as long as you select the Inherit to structure and select the associated Document Types to which the inheritance is assigned.

The administrator can add roles to the Permission Rules for Projects

Projects can have different roles (project manager, client, design) who want to be given role-based rights.

• Different projects may have different users in their roles.
• In this case, the same Permission Rule is suitable for several projects.

The picture below shows how to add a role in Permisson Rule: "Projecs, Products, Customer, Supplier"

• System Administrator > Users and Permissions > Permission Rules > the above rule > View/edit Table

Define a project organization for a project

In the Project Organization section, you can assign roles to a project.

• Project organization managing is possible for all those who have Write permissions for the project.
• That is why it is advisable to carefully design the Permission rules.
  • Only the administrator can edit the Permission rules.

Defining roles

The administrator can define the Permission rules.

Portal > Systems Administration > Users and Permissions > Roles

Role-specific Permissions for projects

When people have been added to the roles of a project, the role-based rights appear in the permission table under their own Role subtitle.

• If no people have been added to the roles, the subtitle Role will not be displayed.
• When you move the cursor over a role, you will see the people who have that role.

Make your own project organization for the subproject if needed

By default, a subproject follows the project organization of the main project, but can be made its own project organization if needed.

If necessary, you can return the Main Project Organization to the subproject.