Launching Workflow Permissions

I’m excited to announce the launch of our latest feature, Workflow Permissions.

Workflow Permissions allows you to more easily control which end-users have access to different features of your integrations. 

Previously, any workflows you created for your integrations on Paragon would be available to all your end-users. This works well if you have a standard set of integration use cases that are commonly shared among all of your users. However, if you wanted to limit certain integration features to certain user groups, or provide custom integration functionality to specific users, there wasn’t an easy way to do so.

Workflow Permissions solves this problem by enabling you to control the visibility of workflows to specific users or groups of users. Now, in the Connect Portal editor, you can easily specify a set of conditions using that a user must meet for them to be able to access the workflow.

‍

This takes advantage of Paragon’s User Metadata API, which allows you to set any arbitrary metadata to users that can then be used in Workflow Permissions. Let’s walk through a few examples of how this feature can be used.

‍

Upsell your users with specific workflows

One powerful use case of Workflow Permissions is gating features based on your users’ billing plans. Integrations can be a powerful upsell lever, with many SaaS companies offering integrations as a paid feature available only on higher billing plans.

If you wanted to limit the availability of certain integration workflows to users on your Enterprise plan, you could use Workflow Permissions to define which workflows should be visible based on the user’s billing plan metadata. For example, HubSpot (which offers a native Salesforce integration) provides standard object mapping capabilities for users on their Professional plan, but require customers to upgrade to Enterprise if they need to map Custom Objects as well. This enables them to increase their revenue by 4x for customers who require custom object mapping capabilities.

Learn how you can maximize the ROI and upsell leverage you create with our integration pricing framework here.

Feature flagging for integrations

Another example of segmenting workflows to certain user groups is if you wanted to release new integration features to a set of beta users before releasing them generally to your entire user base.

In this case, you could use User Metadata to designate which users should have access to these beta features, and Workflow Permissions to designate which workflows should be visible only to beta users.   

Bespoke workflows for specific users

In addition to segmenting workflow visibility to certain user groups, Workflow Permissions can also be used to provide specific workflows to individual users. For example, if you wanted to support bespoke, user-specific use cases for individual enterprise customers, you could use Workflow Permissions to define which workflows should be visible based on a specific user ID or organization name.

Workflow Permissions is just one of many new features we’re excited to share with you this year. If you want to learn more about Workflow Permissions, check out our docs or schedule a demo with us. To keep up with all of Paragon’s new features, subscribe to our newsletter. Thanks, and looking forward to sharing more updates with you soon!