Channel-based Journey and AI Agent permissions

Business problem

Currently, users with access to Journeys or AI Agents can view and modify all created workflows and "On-demand" Journeys, regardless of which channels they manage. This lack of restriction allows users to select or amend Journeys that are not intended for their specific communication channels.

Wished result

Permissions or visibility settings that restrict users to only see and interact with Journeys and AI functionalities that are specifically enabled for the channels they are assigned to.