Creating a separate assignment via workflow - can not inherit the document rights

You can configure the permissions in M-Files Admin in the normal way by modifying the default permissions in the Assignment object type or using automatic permissions in assignment classes. There's one built-in assignment class in every vault but you can create additional classes if there's a need for different permissions for different types of assignments.

Each workflow assignment contains a reference to the related document via the Document property so you can access the document metadata in your assignment access control list, for instance make the assignment visible only to Document.Document owner and Document.Approver if you have such properties.

You can configure the permissions in M-Files Admin in the normal way by modifying the default permissions in the Assignment object type or using automatic permissions in assignment classes. There's one built-in assignment class in every vault but you can create additional classes if there's a need for different permissions for different types of assignments.

Each workflow assignment contains a reference to the related document via the Document property so you can access the document metadata in your assignment access control list, for instance make the assignment visible only to Document.Document owner and Document.Approver if you have such properties.

Hi Joonas!

Ok, it is clear. But as I remember earlier the separate assignments inherit the document rights and onlya one Assignment object type was enough.

Thank You for Your help!

Best regards:

Kornél

I don't recall the exact behavior off the top of my head but feel free to test it. There may be a difference depending on whether you have modified the document's own permissions ("This object" in the object permissions dialog, which defaults to Full control for all internal users for the Document object type) or if you are using automatic permissions.