Grant or Revoke Private Channel Access via Workflow

By Sparkforge Support Team ·Last reviewed May 3, 2026

Sparkforge workflows include Grant Private Channel Access and Revoke Private Channel Access actions for community management. Use them to add or remove members from private channels (and the parent group) automatically.

The Grant and Revoke Private Channel Access actions automate community membership inside Sparkforge workflows. Use them to give a paying member access the moment they buy, or to revoke access when a subscription ends.

Triggers and actions available

Triggers

Private Channel Access Granted
Private Channel Access Revoked

Actions

Grant Private Channel Access — adds a member to a specific private channel inside a community group. If they aren't already a group member, they're added to the group too.
Revoke Private Channel Access — removes a member's channel access while keeping them in the parent group.

Configure the action

Open the Workflow Builder in your Sparkforge account.
Click Create a Workflow.
Add the trigger you want to react to (for example, an order placed).
Add an action and select Grant Private Channel Access or Revoke Private Channel Access.
Choose the community group and the private channel. Only private channels appear in the dropdown.
Add any follow-up actions (welcome email, internal notification, etc.).
Test in a controlled environment, then save and publish.

Example

A book club community sells a paid tier with a Book Upgrades private channel. When a new member buys the tier, the workflow grants channel access automatically, so they receive announcements without manual onboarding.

Frequently Asked Questions

What is the difference between granting group access and granting private channel access?

Granting private channel access adds the member to the channel, and adds them to the parent group as well if they aren't already in it. Revoking only removes the channel access — the member stays in the group.

Can I see public channels in the workflow action dropdown?

No. Only private channels appear, since public channels don't require an access workflow.

What triggers does private channel access produce?

Private Channel Access Granted and Private Channel Access Revoked. You can use either to start a downstream workflow, like sending a welcome email.

How do I test the workflow before going live?

Run it in a controlled environment with a test contact, confirm the member ends up in the right group and channel, then activate it for real members.