Every business process defines proper roles for each activity or step; for example only managers can sign a check over 10, 000 dollars, or only the person who initiated the process can finish it by approving or rejecting something.

OSWorkflow makes security very flexible for the programmer by discriminating step permissions and actions restrictions independently, and using the concept of step ownership to assign tasks directly to some users.

In addition to this, OSWorkflow relies on the OSUser open-source component to manage user authentication and authorization. OSUser has very powerful extension mechanisms; but you are not bound to it, OSWorkflow can use any security package by using Conditions for instance.

First we'll cover step permissions, which allow us to define status or group conditions to restrict entering any workflow process step.