Summary
When a supervisor who does not have the Telephony > Station > Disassociate permission performs a force logout operation, the logged-out user’s station will no longer be automatically disassociated.
Effective Date
Monday, June 22, 2026
Details
As part of the recent effort to introduce permission checks to previously unrestricted station-management endpoints (see related announcement: https://community.genesys.com/discussion/permissions-enforcement-added-to-user-station-management-endpoints), an edge case affecting the force logout feature was identified.
Currently, when a supervisor performs a force logout, the target user’s station is disassociated even if the supervisor does not have the Telephony > Station > Disassociate permission. This behavior is inconsistent with the new permission model.
After this change, station disassociation during force logout will occur only if the acting supervisor has the required permission.
Additional documentation for the force logout feature is available here:
https://help.genesys.cloud/articles/log-an-agent-out-of-genesys-cloud/
Customer Impact
- Supervisors without the Telephony > Station > Disassociate permission will still be able to perform a force logout, but the user’s station association will remain intact.
- Supervisors with the permission will experience no behavioral change.
Organizations that rely on force logout operations to also disassociate stations should ensure that supervisors performing these actions are granted the Telephony > Station > Disassociatepermission.
Impacted Resources
DELETE api/v2/apps/users/{userId}/logout
Issue References
[TC-2366]
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.