Understand Mailbox Exchange database tables
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Identify module-owned data areas.
Where to goTechnical reference — no staff menu route
What this guide helps you do
Identify module-owned data areas. 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
- Tables: accounts, members, folders, threads, messages, categories, attachments, outbox, outbox attachments, templates, autoreplies, autoreply accounts/logs, conversions, receipts/events.
- Use controller/model; no direct SQL.
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.
Related guides
Was this guide useful?Your response is stored only in this browser.