Eloqua Product Notice: Data Export will honor Contact Security [May 2022]

JodyMooney-Oracle

With the arrival of Eloqua release 22B (May 2022), we are modifying Data Export to honor Contact Security based on the User that creates the export.

What’s changing?

With Eloqua 22B, we are modifying Data Export to honor Contact Security based on the User that creates the export.

Timeline

With the arrival of Eloqua release 22B (May 2022), we are modifying Data Export to honor Contact Security based on the User that creates the export. Check the Eloqua Release Center for specific dates and times.

Next Steps

If you are using Contact Security confirm the User that created any contact export has access to all required labels.

Note, the User that created the export will be added to the Data Export area in 22B, until then the User that created the export can be confirmed in the Audit Log area.

Frequently Asked Questions

 Q: What happens if the User that created the export is disabled?

A: The export will still check the User that created the export to confirm access even if the User is disabled.

Q: What happens if the User that created the export is deleted?

A: The export will fail and can no longer be used. A new export will need to be created.

derek.bell

Does this enhancement extend the same restrictions to users exporting data from Insight?

Hal_D

Did you find answers on this, we are looking at how we restrict exporting data in insight.

Jeeves/Bob-Oracle

@derek.bell - No this enhancement does not extend to OBIEE/Eloqua Insight

@Hal_D - If you are looking to restrict exporting of data in Insight, my recommendation would be to not grant access to the user that should not have access. Instead, you can create the required reports that the user needs and have it delivered to their email address via Agents.