Summary
We are adding 4 new permissions that will be used for sequence schedule management to be decoupled from voice schedule management. These permission will be added automatically to those roles where their current counterpart exists.
The following table describes the names of the new permissions, and their counterpart that drives the auto addition of this new permission:
|
New Permission
|
Counterpart Permission
|
|
outbound:campaignSequenceSchedule:view
|
outbound:schedule:view
|
|
outbound:campaignSequenceSchedule:edit
|
outbound:schedule:edit
|
|
outbound:campaignSequenceSchedule:delete
|
outbound:schedule:delete
|
|
outbound:campaignSequenceSchedule:add
|
outbound:schedule:add
|
Further reading about the newly introduced division aware permissions that this sequence schedule decoupling will support is provided underCampaign scheduler to support divisions for improved access control and clarity - Genesys Cloud Resource Center
Effective Date
Monday, August 18, 2025
Details
As part of our effort to provide division awareness to campaign schedules, we have identified that a portion of users are creating sequence schedules that cross division borders.
To ensure we honour this use case, we are adding a new permission that decouples sequence schedule management from the voice campaign management, allowing the former to stay division-unaware while the latter becomes division-aware.
Customer Impact
It does not have imminent impact on customers.
It will take effect when the customer decides that they would like to use voice campaigns in a division aware manner, in which case they will have to remove the outbound:schedules:view, outbound:schedules:edit, outbound:schedules:delete permissions from their roles.
Impacted Resources
GET /api/v2/outbound/schedules/sequences
GET /api/v2/outbound/schedules/sequences/{sequenceId}
PUT /api/v2/outbound/schedules/sequences/{sequenceId}
DELETE /api/v2/outbound/schedules/sequences/{sequenceId}
Issue References
[AUTHZ-801]
Contacts
@Mason Mansfield @Istvan Vajnorak
Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.