Who This Is For / When to Use
This article is for account owners and admins who want to automate private channel access management using Kyrios workflows.
Overview
Kyrios provides dedicated workflow triggers and actions to manage private channel membership automatically. These tools ensure access is granted or removed at the correct time without manual updates.
Available Workflow Triggers
Workflow triggers start a workflow when a private channel access event occurs.
Private Channel Access Granted
This trigger fires when a contact is added to a private channel.
What happens:
The contact is enrolled in the workflow immediately after access is granted.
Filters can be applied to target a specific group or private channel.
Common use cases:
Send onboarding messages after private channel access is granted.
Apply tags or update CRM fields for private channel members.
Private Channel Access Revoked
This trigger fires when a contact is removed from a private channel.
What happens:
The contact is enrolled in the workflow immediately after access is revoked.
Follow-up actions can be automated to maintain access accuracy.
Common use cases:
Send notifications about access removal.
Remove tags or trigger offboarding workflows.
Available Workflow Actions
Workflow actions control whether a contact is added to or removed from a private channel.
Grant Private Channel Access
This action automatically adds a contact to a selected private channel.
Behavior details:
If the contact is not already part of the selected group, Kyrios automatically adds them to the group.
The contact is then added to the selected private channel.
Common use cases:
Grant access after a purchase or form submission.
Add new members to private communities automatically.
Revoke Private Channel Access
This action automatically removes a contact from a selected private channel.
Behavior details:
Access to the private channel is removed immediately.
The contact can remain in the group unless removed by a separate action.
Common use cases:
Remove access when a subscription expires.
Enforce compliance or access rules automatically.
Requirements and Rules
These rules apply to all private channel workflow triggers and actions.
The selected group must contain at least one private channel.
If no private channels exist in the selected group, the workflow cannot be saved.
Removing a contact from a private channel immediately removes access to all channel content and conversations.
Common Issues and Fixes
Workflow will not save
Cause: The selected group does not contain any private channels.
Fix: Add at least one private channel to the group, then reselect the group in the workflow.
Contact not added to private channel
Cause: The workflow action was misconfigured or filtered incorrectly.
Fix: Confirm the correct group and private channel are selected in the action settings.
FAQ
Does granting private channel access also add the contact to the group?
Yes. If the contact is not already part of the group, Kyrios automatically adds them to the group before granting private channel access.
What happens when private channel access is revoked?
The contact immediately loses access to the private channel and all its content.
Can I automate both granting and revoking access?
Yes. You can use both triggers and actions in separate workflows or within the same automation logic depending on your use case.