The Group Access Revoked trigger is activated when a user’s membership in a specific community group is removed. This trigger enables automated workflows to notify users of the change and initiate any necessary follow-up actions, ensuring clear communication and a seamless user experience.

How It Works #

Begin by accessing the relevant workflow, then add the Group Access Revoked trigger.

Workflow Trigger Name #

In the Workflow Trigger Name field, you can rename the trigger to paint a better picture of its intended purpose.

Set Up Filters #

Refine the trigger by specifying the groups from which users should be removed. Use the “is” or “is not” filters to include or exclude specific groups. Additionally, the “is empty” and “is not empty” filters can be used to target users based on whether they currently belong to any groups or none at all.

Save the Trigger #

Review and confirm your setup, then save the trigger.

Finally, test the workflow to ensure it behaves as expected, then activate the workflow so it begins running once the trigger criteria are met. By automating responses to group access changes, you can ensure users are promptly informed and any necessary follow-up actions are seamlessly executed. With customizable filters and straightforward configuration, this trigger helps streamline workflows and enhance the overall user experience.

Frequently Asked Questions #

When does the Group Access Revoked trigger fire? #

It activates when a user’s membership in a specific community group is removed.

What can I automate with this trigger? #

You can notify users of the change and run any necessary follow-up actions automatically.

What filters are available? #

Use “is” or “is not” to include or exclude specific groups, and “is empty” or “is not empty” to target users by their current memberships.

How does it differ from Group Access Granted? #

Granted fires when a user is added to a group, while Revoked fires when their membership is removed.

Should I test before activating? #

Yes. Confirm the workflow behaves as expected, then activate it so it runs whenever the trigger criteria are met.

Why use this trigger? #

It keeps users promptly informed of access changes and streamlines follow-up, enhancing the overall user experience.