Email verification for protected exports
Email verification checks the requesting operator before protected history, report and personal-data exports.
What it is
INSIDE can ask you to verify an export with a six-digit code sent to your registered operator email address. Verification is separate for conversation history, reports and personal data. Permission to export is still required.
Who uses it and why
Operators and supervisors verify protected exports before downloading data. Users with the Settings or Manager role maintain operator email addresses and grant the relevant export permissions.
Where to find it
The verification prompt appears when you start a protected export from conversation history, reporting or Audit. For personal data, the prompt is titled Export Conversation Data and its confirmation button is Verify and Download.
A user with the Settings or Manager role can review Allow History Export and Audit permissions in Settings › Account › Operators.
How it works
- Start the export you need.
- If verification is required, check the registered email address shown in the prompt.
- Enter the six-digit code sent to that address.
- Confirm the code to continue with the export.
An incorrect code produces an error and shows how many attempts remain. After three incorrect attempts, the prompt tells you to wait one hour. History and report code requests check the one-hour lock; the personal-data request flow handles this differently.
Successful verification is reused for that operator, website and export category for the rest of the website's calendar day. Verifying a report export does not also verify a history or personal-data export.
Configure it
Check the operator's registered email address before exporting. A user with the Settings or Manager role can grant Allow History Export for operators who need history downloads; it is off by default. For personal-data export controls, ask them to review Export within Audit permissions.
There are no client Settings controls for the three-attempt threshold or the one-hour lock duration. Powerfront can investigate email delivery or unexpected verification behaviour.
Permissions
| Permission | Lets you |
|---|---|
| Allow History Export | Allows an operator to export conversation history after the required verification; off by default. |
| Export | Shows the personal-data export action within Audit permissions. |
Limits and good to know
- A code goes to the requesting operator, not the customer whose data is being exported.
- A recent outstanding code may be reused instead of sending another email. Reopening the prompt does not always generate a new code.
- Verification does not grant additional report, website or history access.
- The personal-data flow does not apply the same lock check as the history and report code-request flows. Do not rely on identical lockout behaviour across all exports.
Depends on and works with
View all connections as a list
This feature uses
- Operator accountsConfigured by
Verification uses the requesting operator's registered email address.
- Roles and permissionsConfigured by
Export permissions are separate from successful email verification.
- Operator settingsConfigured by
Allow History Export is a separate operator setting needed for conversation-history downloads.
- Conversation history and searchRelated
Conversation-history exports use their own email-verification category.
- Report downloads and email sharingRelated
Report downloads and email sharing use a separate report-verification category.
- Personal data exportRelated
Personal-data export uses the Audit verification category, separately from history and reports.
Used by
- Report downloads and email sharingRequires
Protected report exports require verification through the operator email address when prompted.
- Audit search for retained customer recordsRelated
Audit exports use personal-data email verification, separately from report export verification.
- Personal data exportRequires
Personal-data export requires verification of the requesting operator's email.
- Sign-in and chat request limitsRelated
Protected exports have their own verification-attempt limits, separate from sign-in and chat limits.
FAQ and troubleshooting
Why have I not received a code?
Check the email address shown in the prompt and your junk folder. If it is correct and the message does not arrive, ask Powerfront to investigate delivery.
Why am I asked again after verifying a different export?
History, reports and personal data use separate verification categories. Verification also needs to be renewed on a later website calendar day.
Why am I told I cannot export history after entering the code?
Your account also needs Allow History Export. Ask your Settings administrator to review it.
What should I do after too many incorrect attempts?
Follow the prompt to wait one hour, then reopen the export and use the code associated with that export category.