AI assistance, CRM conversion, read receipts and attachments

Protect personal information in Mailbox Exchange AI workflows

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Apply authorised external-provider controls.

Audience: Mailbox Exchange usersPermission: Administrator and mailbox ownerModule v1.0.0

Jump to steps

Where to goAdmin Area → Mailbox Exchange → Settings and Accounts → AI

What this guide helps you do

Apply authorised external-provider controls. The workflow below follows the supported application or module flow and does not invent a menu or bypass validation.

Follow these steps

Go to the exact navigation path shown above.
Select the authorised mailbox, message or configuration record.
Complete the fields or action described in this guide.
Save or submit once, then verify the resulting status and related record.

Fields and options

This workflow does not expose additional user-entered fields.

Rules and limits

PII redaction option exists and defaults off.
Email content can be sent to OpenAI.
Use only approved content/provider and verify effective redaction state.

Check it worked

The requested Mailbox Exchange record is updated through the supported controller and remains attributable to the acting staff member.

Security, audit and troubleshooting checks

Use the exact authorised account, role and record before saving or sending.
Verify the saved status and downstream record; a browser success message alone is not sufficient evidence.
Never expose passwords, API keys, access tokens, protected attachments or raw server paths in support tickets.
Do not edit module or core database records directly to bypass validation, permissions, migrations or state rules.

Was this guide useful?Your response is stored only in this browser.