Looking for some advice on troubleshooting this permission block while migrating agent notes from Zendesk to Genesys Cloud Screen Pops. We are attempting to populate the interaction.screen object with historical context from Zendesk tickets using the POST /api/v2/analytics/screen-recordings endpoint. The flow triggers successfully from Architect, but the API returns a 403 Forbidden error with the message “User lacks required permissions for screen recording ingestion.” I have verified that the user role has screen:recordings:view and screen:recordings:write enabled, which should theoretically allow data ingestion for migration purposes. The environment is Genesys Cloud EU-1, running the latest patch. Unlike Zendesk’s straightforward API write access, Genesys Cloud seems to enforce stricter scopes for screen interactions. The payload includes a valid interactionId and screenSessionId, yet the rejection persists. Is there a specific admin setting or a hidden permission like screen:recordings:ingest that overrides the standard write permissions? This blockage is halting our digital channel migration timeline, as we cannot populate the screen pop context without these historical notes. How do other migration specialists handle the initial data load for screen recordings when standard write permissions appear insufficient?