The Telephony > Phone > Assign permission will not disappear, this permission is used (only) for updating and deleting a user's default phone and that use will continue as before, unchanged. I've got a ticket in the works to update the description of that permission in the Genesys Cloud UI to better reflect its purpose, thank you for drawing attention to it.
Original Message:
Sent: 02-24-2026 05:52
From: mizuki toyoshima
Subject: Backfill of User Station and Call Forwarding Permissions
Hi Daniel Meyer
Thank you for reply.
I think the following two newly added permissions have the same content as "Telephony > Phone > Assign," but what will happen to the old permission ("Telephony > Phone > Assign")? If the old permission does not disappear, how should they be used differently?
Telephony > Others' phone associations > Edit (new)
Telephony > User's phone associations > Edit (new)
best regards,
------------------------------
mizuki toyoshima
-
Original Message:
Sent: 02-20-2026 11:11
From: Daniel Meyer
Subject: Backfill of User Station and Call Forwarding Permissions
Hi Mizuki, and thanks for the questions.
First, note that the organization Role Backfill setting does not control the type of backfill mentioned in the original post, which will be performed for each organization irrespective of that setting. Each role that contains Conversation > Call > Add permission will get the six additional permissions backfilled into the role.
Since in the case you describe Conversation > Call > Add is assigned to all users, the other questions are moot as all users will benefit from the backfill operation.
However, for completeness, if a user does not have any roles that contain Conversation > Call > Add...
Administrators
This depends on how the organization uses roles.
If the admin has one of the Genesys Cloud default roles:
- By default the Telephony Admin default role has Telephony > All Permissions and users with this role will automatically retain the permissions to edit their own and others' phone associations.
- The Communicate - Admin, Supervisor, and Outbound Admin default roles have been updated to include permissions to edit their own and others' phone associations.
If the administrators are using custom roles, then the situation is as follows:
- If the custom role has Telephony > All Permissions it automatically has these new permissions as well, no manual intervention needed; and if the custom role has the Conversation > Call > Add permission it will be backfilled with the six listed permissions, no manual intervention needed.
- If the custom role lacks Telephony > All Permission AND it does not have the Conversation > Call > Add permission, it will not automatically get/have the new permissions. If none of the roles the admin has will get the new permissions, the permissions will need to be manually added to a role the admin has so that the admin does not lose the ability to edit phone associations.
Agents
Once the permission checks are enabled, agents must have Telephony > User's phone associations > Edit to continue to be able to change their own phone associations. (i.e. if they don't have that permission they will lose the ability to change their phone associations.)
Let me know if you have further questions.
Thanks!
Daniel
------------------------------
Daniel Meyer
Original Message:
Sent: 02-19-2026 01:33
From: mizuki toyoshima
Subject: Backfill of User Station and Call Forwarding Permissions
Currently, "role backfill" is disabled, and the "Conversation > Call > Add permission" is assigned to all users.
- Administrators currently add and edit operators' telephones from "Digital and Telephony > Telephony > Phone Management".
- Operators currently change their own telephone associations from the user icon in the upper right corner of the screen after logging in.
Please let us know the following two points:
- Is it correct to understand that even if the following newly added permissions are not granted, the administrator's ability to add and edit telephones (such as assigning them to users) will not be affected?
- Telephony > Station > Disassociate
- Telephony > Others' phone associations > Edit
- Telephony > Others' phone associations > View
- Telephony > User's phone associations > Edit
- Telephony > User's phone associations > View
- Conversation > Call Forwarding > View
- Is it correct to understand that even if the following newly added permissions are not assigned, operators will still be able to change their own telephone associations as before?
- Telephony > User's phone associations > Edit
-Telephony > User's phone associations > View
Mizuki Toyoshima
------------------------------
mizuki toyoshima
Original Message:
Sent: 01-12-2026 12:52
From: Developer Community
Subject: Backfill of User Station and Call Forwarding Permissions
Summary
For roles that currently include the Conversation > Call > Add permission, the following six permissions will be automatically added (backfilled):
- Telephony > Station > Disassociate
- Telephony > Others' phone associations > Edit
- Telephony > Others' phone associations > View
- Telephony > User's phone associations > Edit
- Telephony > User's phone associations > View
- Conversation > Call Forwarding > View
Timeline
- Backfill performed: On or after February 16, 2026
- Permissions enforcement enabled: On or after March 1, 2026
Effective Date
Monday, February 16, 2026
Details
This backfill ensures that existing users retain access to the affected APIs once user station permission enforcement is enabled. It is intended to prevent disruption for users who already have the appropriate level of access through the Conversation > Call > Addpermission.
Customer Impact
- For the typical scenario where users calling the affected endpoints already have the Conversation > Call > Add permission, no impact is expected. The required permissions will be backfilled before permission checks are enforced.
- If a user accesses these endpoints without the Conversation > Call > Add permission, an administrator will need to update the relevant roles to avoid request failures once permission enforcement is enabled.
Additional guidance is available in the related forum post:
Permissions Enforcement Added to User Station Management Endpoints
Impacted Resources
Existing Endpoints
• GET /api/v2/users/{userId}/callforwarding
• GET /api/v2/users/{userId}/station
• PUT /api/v2/users/{userId}/station/associatedstation/{stationId}
• DELETE /api/v2/stations/{stationId}/associateduser
• DELETE /api/v2/users/{userId}/station/associatedstation
New Endpoints
• GET /api/v2/users/stations/me
• PUT /api/v2/users/stations/me/associatedstation/{stationId}
• DELETE /api/v2/users/stations/me/associatedstation
Issue References
[PURE-6104]
Contacts
@Daniel Meyer
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.