Workflow Start and Report

Basically, the authorisation in the Custom UI is in accordance with the TrackingOne authorisation concept insofar as TrackingOne functionality or resources are concerned: A user is allowed to do any TrackingOne action exposed by a custom user interface which he or she is allowed to do in the TrackingOne application as well.

For example: A user may or may not start a workflow if he or she does so in TrackingOne. More precisely, he or she needs the role T1_User, the T1_User role extension for the container to which the workflow belongs, and a T1_User role extension for any category to which the workflow is assigned.

A user may or may not generate a report if he or she does so in TrackingOne. More precisely, he or she needs the role T1_Analyst, the T1_Analyst role extension for the container to which the report belongs, and a T1_Analyst role extension for any category to which the report is assigned.

Please refer to the TrackingOne documentation to learn more about roles and role extensions in TrackingOne.