I've added one more affected endpoint:

GET /users/{userId}/callforwarding - will now require conversation:callForwarding:edit

This one will be backfilled as well for existing users.

Hi yuueno,

The backfill will be performed by Genesys staff using an internal automated process, and yes, the new permissions will be added to roles automatically, i.e. no manual process needed to maintain the abilities a user had before. The manual process will be for sys admins to then revoke the permissions from whoever should not have them - an ability they do not currently have.

Hi Daniel,

I have a question about your comment below.

with the permissions backfill (which Genesys will perform immediately before the feature is turned on) users will actually already have the new permission,

How will this backfill be performed?
These new permissions are added in all roles automatically?

Austen:

this won't affect calls to GET /api/v2/users/{userId} that use the "station" expand parameter, correct?

Correct, the new permissions do not affect that expand parameter.

DeeQ:

all we have to do is update our environment to make sure the new permission is granted if required

Technically it's the opposite: with the permissions backfill (which Genesys will perform immediately before the feature is turned on) users will actually already have the new permission, for continuity of system behavior; at that point admins have the option of revoking the permission from users for whom the permission is not required.

jhwon:

put /api/v2/users/{userId}/station/associatedstation/{stationId}

You are correct, where the posting said PUT api/v2/users/{userId}/station/{stationId} it should have said PUT api/v2/users/{userId}/station/associatedstation/{stationId}. I've fixed the original post, thanks for calling this out.