To maintain multiple lines of business in Hyperscience, you may need to create separate flows for each line of business. With flow-based permissions, you can restrict access to a flow so that only users in certain permission groups can access:
the flow itself,
submissions sent to the flow,
documents processed by the flow,
the release assigned to the flow, the release's Classification model and layouts, the Field Identification models for those layouts, and
Supervision and QA tasks created from the flow.
Currently, flow-based permissions do not create flow-based restrictions for viewing reporting data.
The specific actions a user can perform are determined by the specific permissions given to their permission group, as well as any task restrictions that are in place.
Because flow-based permissions restrict access to a flow's models and tasks, they help you make sure that the performance optimizations you make for one flow do not affect the performance of other flows.
Setting up flow-based permissions
You can give a permission group access to a live flow by going to its configuration page and selecting the flow under Assign Group Access to Specific Flows. Flow-based permissions do not apply to the System Admin permission group, as those users can access all flows in the instance.
To learn more about editing permission groups, see Managing Permission Groups.
You can give a permission group access to multiple flows, and multiple permission groups can have access to a flow.
If a flow has not been assigned to a permission group, any user can access the flow. For example, any keyer with the Complete Identification permission can complete Identification tasks created from that flow.
Tasks and changing flow-based permissions
When a task is created, the flow-based permissions in place at that time are applied to the task.
For example, If you restrict access to a flow, and the system has already created tasks from that flow, the flow-based permissions are not retroactively applied to those tasks.