Who This Is For / When to Use
This article is for admins who want to automate access to private community channels without manual intervention. Use this when managing gated content, VIP communities, paid memberships, or role-based access inside Communities.
What Private Channel Workflow Triggers Do
Private Channel workflow triggers automatically start a workflow when a contact is granted or revoked access to a private community channel.
These triggers allow workflows to respond immediately when access changes, enabling automated onboarding, notifications, or follow-up actions tied to private channel membership.
Available Triggers
Private Channel Access Granted
Private Channel Access Revoked
How to Create a Private Channel Workflow
Creating a private channel workflow starts from the Workflow List and uses standard workflow setup steps.
Step 1: Create a New Workflow
Go to Automation → Workflows.
Click Create Workflow.
Select Start from Scratch.
How to Configure a Private Channel Trigger
Triggers define when the workflow should run.
Step 2: Add a Trigger
Click Add New Trigger.
Search for Private.
Select Private Channel Access Granted or Private Channel Access Revoked.
Step 3: Apply Trigger Filters
Filters limit the workflow to a specific group or private channel.
You can filter by:
Group (required for accuracy)
Private Channel (recommended)
This ensures the workflow only fires for the intended community and channel.
What Private Channel Actions Do
Private Channel actions control access by adding or removing contacts from private channels automatically.
Available Actions
Grant Private Channel Access
Revoke Private Channel Access
These actions execute immediately when the workflow runs.
How to Grant Private Channel Access with a Workflow
Step 4: Add the Grant Access Action
Click the + icon under the trigger.
Search for Grant Private Channel Access.
Select the action.
Step 5: Configure the Action
Select the Community Group.
Choose the Private Channel.
Save the action.
If the contact is not already a member of the group, Kyrios automatically adds them to the group before granting channel access.
How to Revoke Private Channel Access
The revoke process follows the same steps as granting access.
Add a new action.
Select Revoke Private Channel Access.
Choose the same group and channel.
Save the action.
Access is removed immediately after the workflow executes.
Publishing and Testing the Workflow
Workflows must be published before they run.
Click Test Workflow to validate logic.
Toggle Draft → Publish.
Save the workflow.
Common Use Cases
Paid Membership Access
Grant access to premium channels when a user purchases or upgrades a plan.
Event or Program Channels
Automatically add users to private channels for cohorts, masterminds, or live programs.
Role-Based Communities
Revoke access when a user’s role changes or membership expires.
Onboarding Automation
Grant access immediately after signup or approval without manual admin work.
Common Issues and Fixes
Workflow Does Not Trigger
Cause: Filters are too broad or missing a group or channel.
Fix: Always apply both Group and Private Channel filters.
Grant Action Fails
Cause: The selected group has no private channels.
Fix: Create at least one private channel in the group before configuring the workflow.
No Notification Sent
Cause: No messaging action was added.
Fix: Add an Email, SMS, or Internal Notification action after the access action.
FAQs
What happens if a user is not part of the group?
Kyrios automatically adds the user to the group before granting private channel access.
Can I grant access to multiple private channels?
Yes. Add multiple Grant Private Channel Access actions within the same workflow.
Does revoking access delete user data?
No. The user remains in the group, but loses access to the private channel content.
Can I move users between private channels automatically?
Yes. Use a Revoke action followed by a Grant action in the same workflow.
Do private channels need to exist first?
Yes. A private channel must already exist in the group for the workflow to function.