Genesys Cloud
Deprecation: Permission enforcement change to update another user’s presence with the PATCH API

Starting July 20, 2025, Genesys Cloud will require that users have the presence:userPresence:edit permission to update another user’s presence.

Currently, users could update another user’s presence in an undocumented manner with the PATCH API. The permission enforcement resolves this issue. Users can still use the PATCH API without this permission until July 20, 2025. Starting April 21, 2025, users can add the presence:userPresence:edit permission so that they can update another user’s presence even after July 20, 2025.

For more information, see Presence APIs in the Developer Center.

Preguntas frecuentes

¿Qué significa esto?

Between the announcement date and the effective date, customers that rely on the PATCH API to update presence must add the presence:userPresence:edit permission to continue this functionality. After July 20, 2025, Genesys Cloud will require this permission to use the PATCH API to update another user’s presence.

¿Me afecta?

If you or anyone in your organization uses the following endpoints to update other user’s presence, you will be impacted:

PATCH /api/v2/users/{userId}/presences/purecloud
PATCH /api/v2/users/{userId}/presences/{sourceId} 

¿Qué debo hacer antes de la fecha de eliminación?

Between now and the effective date, Genesys recommends that anyone working with the PATCH API add the presence:userPresence:edit permission.

¿Qué pasa si necesito ayuda o tengo preguntas?

Contacto Mi apoyo.