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, take the cursor over the group.

You see what the Permissions mean

Take the cursor over the radio Button, so the program tells you more about the permissions.

See the title who has the Permissions

Move the cursor over the Permission so that the program lists the users with the Permission.

Other Permissions tells about the permissions of the owner and the founder

• By default, the document founder gets the Write permissions they have added to the document (as before).
• Others have no permissions to it unless the Permissios Rules provide them.
• The person you set as the owner gets the Write permission 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, leaving the owner's permissions out of himself.

The Connection permissions 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 rights are set by the Radio Button and not by the Check Box.
• Below is the new and old Permission Table.
  

You can let inherit hierarchical rights to other related objects of this projects

Previously, you may have inherited hierarchical rights to drawings, models, and documents. 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 the 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 the 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 give 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 a role in adding Permisson Rule: "Projecs, Products, Customer, Supplier"

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

Define a project organization for the project

In the Project Organization section, you can assign roles to the 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

The Role specific Permissions for projects

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

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