Beta

This feature is in open beta. It’s available for use but still in active development and may change.

You can enable Zap restrictions in your account to keep your important data secure. When enabled, account members will have to request approval from a super admin or owner to make certain changes to a Zap. This includes:

• Publishing.
• Editing.
• Adding step notes to.
• Turning off.
• Deleting.

Pre-requisites

• You must be a super admin or owner to approve or deny requests.

Enable publishing restrictions

1. In your account settings, under the Admin settings section, select Members to be redirected to the Members page.
2. Select the Approval rules tab.
3. In the Publishing restrictions section, click to toggle the switch on.

Approval rules

By default, only super admins and account owners can approve Zaps. To allow admins to approve:

1. Under the Who can approve field, click to expand the dropdown menu.
2. Select Admin, super admin and account owner.
3. Click Save rules to confirm your change.

By default, all Zaps will require approval before publishing. To limit approvals by certain criteria:

1. Below the Who can approve section, select Only require approvals for Zaps meeting the following criteria.
2. A new field, Apps requiring approval will appear below.
3. Search for and select the apps you want to require approval for before publishing.
4. Click Save rules to confirm your change.

Once enabled, a dropdown menu will appear prompting members to request approval before they can change their Zap. They must provide a description of why they’re requesting the change. All super admins and the account owner will receive an email notification of the request. This setting will apply to all future attempts to change Zaps, including in existing Zaps.

Members can also delete their own approval requests. If they do, Zapier will not notify super admins or the account owner that the request was deleted. The request will no longer appear in the pending approvals list.

Note

• If publishing restrictions are not enabled, admins, super admins, and the account owner can publish, edit, add step notes to, turn off, or delete a Zap without requesting permission.
• If publishing restrictions are enabled, only super admins and the account owner can publish, edit, add step notes to, turn off, or delete a Zap without requesting permission.
• All pending requests will be deleted if you change your approval rules.

View requests

You can view pending approvals requests in the Versions section of the Zap editor's left sidebar and in the Pending approvals request page. Super admins and owners can view all requests that are pending approval, as well as their own requests for approval. Admins and members can only review their own requests. Learn more about user roles in Enterprise accounts.

Approve or deny a request

All super admins and the account owner will receive an email notification from Zapier with the request. Any super admin or the account owner can approve or deny a request.

Notification email

In the notification email, you can either:

• Click View Zap in editor to view the pending request in the Zap editor.
  • You will be redirected to the Versions section of the Zap editor.
  • The request will appear at the top of the left sidebar.
• Click Review request in the notification email to view all pending requests. You will be redirected to the Pending approvals request page.
  • Approvals appear in chronological order, with the newest request at the top.
  • You can also access the Pending approvals request page from the left sidebar in your account dashboard.

Approve a request

To approve a request:

• Click Approve. A dialog box will appear.
• (Optional) In the Message to requester field, you can provide an explanation for why you approved the request.
• (Optional) You can expand the Review changes section to compare an outline of the current draft to the current published version, if one exists.
• Click Approve and publish.

Deny a request

To deny a request:

• Click Deny. A dialog box will appear.
• In the Message to requester field, you must provide an explanation for why you approved the request.
• (Optional) You can expand the Review changes section to compare an outline of the current draft to the current published version, if one exists.
• Click Deny request.

After a request is approved or denied, the member will receive an email notification. If the request response included an explanation, the notification will include it.

Super admins and the account owner can also review individual pending requests in the Zap editor's Change history section. They can also review all pending requests across the account on the Pending approvals request page.

Limitations

• Members can only submit one request per Zap, regardless of request type.
  • Other members cannot submit the same request for the same Zap until the original requestor cancels the request or its approved or denied.
  • Only the member who submitted a request, super admins, and the account owner can edit or replace a draft while approval is pending. Other members cannot.
• Zaps can only have one of each request type pending approval. The 3 types are:
  • Publish a draft (includes adding step notes to a Zap).
  • Turn a Zap on or off.
  • Delete a Zap.
• Members cannot make a request to delete multiple Zaps from the Zaps page.
• Only the member who submitted a request can delete the request.
  • Zapier will not notify super admins or the account owner that the request was deleted.
  • The request will no longer appear in the pending approvals list.
• If a Zap contains a restricted app, members cannot submit requests to publish the Zap.
• Super admins and the account owner can change a draft before approving it for publication.
  • Any and all app connections must be shared with them first. They cannot view or edit Zaps steps that use a private app connection beyond the Setup tab.
• If a super admin or the account owner approves a Zap for publication, they will appear as the publisher of the draft in the Zap version.
• All pending requests will be deleted if you change your approval rules.
• If Zapier turns a Zap off due to issues like errors or billing matters, members must request approval to turn the Zap back on.

Exemptions

• If publishing restrictions are enabled, only super admins and the account owner can publish, edit, add step notes to, turn off, or delete a Zap without requesting permission.
  • If publishing restrictions are not enabled, admins, super admins, and the account owner can publish, edit, add step notes to, turn off, or delete a Zap without requesting permission.
• Users do not need to submit approval to:
  • Change the Zap owner.
  • Rename the Zap.
    • You cannot rename a step while a publish approval request is pending. You must wait until the request is approved, denied, or deleted.
  • Rename previous versions of the Zap.
  • Duplicate a Zap.
  • Enable or disable your Zap’s advanced settings.
  • Replay past runs.
• Any Zaps that exist before publishing restrictions are enabled will continue as is.
  • Once a member attempts to edit, add step notes to, publish a version of, turn off, or delete the Zap, the restriction will be enforced.
• Publish approval is an account-wide setting, but any Zaps moved into the account from another account are not subject to the new account’s setting.

Example

• If a member submits a request to publish a Zap, they cannot submit any other requests for that Zap, like a deletion request.
• If a member submits a request to publish a Zap, no other member can submit a request to publish the same Zap until the original request is approved or denied.
  • But anyone can still request to turn off or delete the Zap.