AutomatorWP Block Users

Description

The Block Users addon adds a “Block Users” box to the edit screen of each AutomatorWP automation, allowing you to select roles and specific users who are prevented from completing that workflow. This granular control is useful when you need to restrict triggers and actions to specific profiles, preventing administrators, editors, or test accounts from firing automations designed for end clients or students.

Main Features

• Role-based blocking: prevents users in selected roles (administrator, editor, author, subscriber, and any custom role) from completing the automation.
• Specific user blocking: selects individual accounts by name or ID to exclude them from the workflow, without altering the WordPress role.
• Selective application per automation: restrictions apply only to chosen automations, keeping other workflows open to all users.
• Native metabox in editor: the setting appears as a metabox within the automation edit screen, with no separate admin screens.
• Compatibility with triggers and actions: works with any combination of triggers and actions registered by other AutomatorWP addons.

Benefits of Block Users

• Control over who triggers automations: stops administrative or internal accounts from launching rewards, emails, or integrations intended for customers.
• Cleaner tests: allows you to exclude QA and developer users from production automations without disabling the workflow.
• Less operational rework: reduces unintended triggers that would require reverting points, badges, emails, or charges in AutomatorWP.
• User role segmentation: separates workflows for students, members, affiliates, or buyers based on the role assigned in WordPress.

Who Is Recommended?

• Administrators using AutomatorWP on course, community, or membership sites who need to isolate internal staff from automations.
• Agencies delivering automations to end clients who want to avoid triggers from support or development accounts.
• Gamification and loyalty program operators who segment rewards by user role.

Recommended for those already maintaining active automations in AutomatorWP and needing a simple exception layer for roles and specific users without rewriting flow logic.

Frequently asked questions