Workflow Access

Modified on Tue, 23 Jul at 7:01 PM

Within an organization, some processes should be known by all members, while others should be restricted to specific individuals, teams, or departments. Additionally, for some workflows, you may need to grant editing abilities to all organization members within Procify, while for other workflows you may need to allow editing rights to only a select few.


To address these needs, Procify has implemented workflow permissions that enable you to manage who can view and edit each of your organization’s workflows. 


To configure your workflow access permissions, head to any workflow in the Workflow Builder, click on Settings, and find the Workflow Access tab, as shown below. In this tab, you are able to view the users who have access to the workflow and make any necessary changes as per your preferences. 




When a workflow is initially created, by default, only the person who created it has viewing and editing access. Admin users have default viewing and editing access to all workflows across the organization.




 


Anyone in the Organization

When the workflow permission is set to ‘Anyone in the Organization’, then all users who have access to the workflow builder, will be able to view or edit - depending on which option is selected - this particular workflow. 




Restricted Access

When the workflow permission is set to ‘Restricted Access’, then only the users who we give access to, will be able to view or edit - depending on which option is selected for each user - this particular workflow.



If you have given someone permission that you want to revoke, simply locate the user from the list of users with access and select 'Remove Access' from the dropdown menu. 




While certain users may not be able to view or edit a specific workflow, they can still initiate cases from them.




 




Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article