Skip to main content
All CollectionsWorkflowReviewing Workflows
Workflow Viewing Permissions
Workflow Viewing Permissions

Viewing Permissions of Workflows to determine who CAN and CANNOT view information provided within a form

Thomas Stallings avatar
Written by Thomas Stallings
Updated over 2 years ago

ARMS is able to limit users ability to view information submitted within a workflow. This will be determined based on the PROCESS ROLE an ARMS User has. Workflow viewership can be granted in multiple levels.

1.) Ability to view all fields within a form. This will allow users to be able to click into an already existing workflow (completed or still within the approval process) and view all fields within this form. An example of what the user would see is below.

2.) Ability to view certain fields within the form. This will allow users to be able to click into an already existing workflow (completed or still within the approval process) and view specific fields within the form. We have the ability to grant viewing permission at an individual field level. This will allow any parts of the workflow to be available or hidden from specific process roles. This will look exactly like the picture above, with the field(s) you want hidden, removed.

3.) Ability to hide all fields within a form. This will limit viewership on all fields filled out within this form. This is most commonly used on forms collecting sensitive information where only a handful of individuals need to be able to view it. For process roles who are not able to view information within a workflow, the screen below will be what appears when they try to click into the form.

NOTE - If you currently are unable to view fields within a workflow and need viewing permission, please reach out to your System Administrator on-campus to request the correct viewing permissions needed to view this workflow in ARMS.

If you have any forms that need to be updated with viewing permissions, please reach out to ARMS Support at help@armssoftware.com and we can limit viewing permissions as needed!

Did this answer your question?