At the moment when a normal user tries to open a model that is being called by a call activity using the Launch editor or blue arrow, if that user doesn't have Start permission for that model, it will not open.
Jason said currently it's all based on the create permission on a process instance which is basically start. it comes from this api call /processes.
and the reason it was implemented this way is because if you have access to edit process A, and you don't have access to start process B, we need to prevent you from using process B as a called activity from process A, since doing so would violate the permissions model.
however, if you are not editing processes or configuring call activities, it would be good if the user could still click through from process A to process B to view it even though he doesn't have the Start permission on process B.
At the moment when a normal user tries to open a model that is being called by a call activity using the Launch editor or blue arrow, if that user doesn't have Start permission for that model, it will not open. Jason said currently it's all based on the create permission on a process instance which is basically start. it comes from this api call /processes.
and the reason it was implemented this way is because if you have access to edit process A, and you don't have access to start process B, we need to prevent you from using process B as a called activity from process A, since doing so would violate the permissions model.
however, if you are not editing processes or configuring call activities, it would be good if the user could still click through from process A to process B to view it even though he doesn't have the Start permission on process B.