Skip to main content
All CollectionsRoles and PermissionsTailoring Custom Permission Sets
Managing Access to Webhook and Zapier Settings
Managing Access to Webhook and Zapier Settings
Updated over a week ago

Productive offers customizable permission sets to effectively control access to Webhook settings (found in Settings > Webhooks) and manage Zapier triggers within your organization.

Check out this guide to learn how to configure custom permission sets, ensuring that only authorized users can manage these settings.

Custom permission sets are available on the Ultimate subscription plan.

Setting Up Custom Permission Sets

1) Creating a New Permission Set

To begin, navigate to Settings > Permission sets and select + New permission set.

This will allow you to build a tailored set of permissions that you can assign to your users.

2) Adjusting Permissions for Webhook and Zapier Trigger Settings

The permissions controlling access to webhook settings and Zapier triggers are found under the "Administration" section.

  • Manage your own Zapier triggers
    This permission allows users to set up and manage their own triggers through Zapier. Although Zapier triggers are not displayed in the Productive interface under webhooks, this permission is needed to configure triggers and access data through Zapier.
    โ€‹

  • Manage webhooks
    This permission controls access to the webhooks configuration in Productive. Users with this permission can set up, edit, and delete webhooks that enable integration with external services.

3) Default Permission Sets

Productive includes system default permission sets, which provide a starting point (base permission set) when creating your custom permission set.

These default sets have pre-included permissions, making it easier to decide which base set to use.
โ€‹Note: Contractor permission set cannot be adjusted with custom permissions.

4) Finalizing and Applying Permissions

Once you've configured the permissions, save your new permission set and assign it to the appropriate users.

Example Use Case: Controlling Access to Data Integrations

Imagine your organization uses webhooks to integrate Productive with a third-party project management tool, syncing important data in real time.

You only want senior developers or IT administrators to be able to configure or modify these webhooks because incorrect settings could disrupt critical workflows.

Additionally, your marketing team uses Zapier to automate tasks between Productive and other apps, like syncing new deals with your CRM.

You want to allow marketing managers to manage their Zapier triggers without giving them access to the webhooks or other sensitive settings.

By creating a custom permission set, you can allow the marketing team to manage their Zapier triggers while restricting their access to webhooks.

At the same time, IT administrators will have full control over both webhooks and Zapier triggers.

This ensures each team only has access to the tools they need, maintaining data security and workflow integrity.

Did this answer your question?