Understand Mailbox Exchange demo mode restrictions
This guide explains that which actions are blocked by MAILBOXAI_DEMO.
Where to goAutomatic module guard — no separate menu route
What this guide helps you do
Know which actions are blocked by MAILBOXAI_DEMO. 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
- Demo mode blocks synchronisation, sending and modifying routes.
- AI actions and approved read-only table requests remain available.
- AJAX returns the demo-disabled message; page actions set a warning.
- Demo mode is not a production permission boundary.
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.