Overview
When you create a separate assignment in a workflow state, the assignment will inherit the permissions from the object in the workflow. However, if you also change the permissions of the object in the same workflow state, you will see that the assignment will get the permissions that the object had in the previous state. This happens because the assignment is created before the permissions are changed in the workflow state (see the order of the state actions in the user guide: https://www.m-files.com/user-guide/latest/eng/State_actions.html).
Solution
If this is an issue in your workflow, you can get around it this way:
1. Add a new state before the state that creates the assignment.
2. Set the new state to change the permissions and then move automatically to the state that creates the assignment.
3. Don't change the permissions anymore in the state that creates the assignment.
