The security model in SCM is role-based. This is similar to the way in which we produce the solution design, where we design processes alongside the role that would perform them. The security model is designed using roles and duties, which in turn have the required privileges. The phrasing of a functional requirement would be written as The service order clerk will create new service orders. The role is Service order clerk, while the duty is Create new service orders. The duty implies that the user needs to have a create privilege on the service order table.
Whenever a solution is designed, even independent software vendor (ISV) solutions, we will have roles and duties in mind so that we can create security elements when the solution is written. So far, we haven't created any security elements so that we could focus on the recipes' tasks.
This does not mean...
