Skip to main content

Configure folder and label sorting

MailGen folder and label sorting supports Google and Microsoft mailboxes. Prepare Google access or Graph access first. Provider label creation, sorting rule storage, and automatic processing are separate actions.

Edit a rule​

  1. In Mail, open Settings → Folders or Labels.
  2. Open an owned folder or label. For a new Google label, wait for creation confirmation.
  3. Open Sorting. Enable Target enabled. Then configure conditions.
  4. Choose Save sorting rules.

The outer Save button saves other folder/label fields. Reading rules requires mail.sorting.read. Saving requires mail.sorting.manage, mail.crud, and access to the mailbox and target. A permission-load failure shows an error rather than silently hiding the editor.

This editor belongs to the working folder/label sorter. The separate block-based Rules/RuleMaker interface does not implement the same complete execution path. A visible Rules page alone does not create working automation.

Enable automatic processing​

On Sorting, enable Folder sorting, Label sorting, and Automatically on arrival as required. Choose Save settings. A rule save alone does not enable automatic work.

Automatic processing needs an allowed sorting model, including for text-only conditions. Feature permissions and model grants are separate. No allowed default model can mean the account lacks access to an existing model.

For Google, automatic admission covers a new non-draft Inbox message first observed during incremental synchronization. Full onboarding, updates to existing messages, and moving an existing message into Inbox do not create a new arrival run. Track the durable state on Sorting. Queue entry is not completion.

Grant the required model​

  1. Open Administration → LLM models (/admin/llm-models). Read the configured sorter model, reasoning, and context values.
  2. Open Administration → Groups and select the appropriate existing group containing the user.
  3. Under Model access, choose Add model access and select that model. Check the selection because the field can preselect another model.
  4. Allow the required Reasoning levels and Maximum context tokens. Use Provider default when the model exposes no explicit level.
  5. Choose Save group and wait for Group saved.

The user must then refresh Sorting. The user must check the model and save automatic settings again. Model changes require another check of reasoning and context fields.

The grant affects every member of that group. Editing requires admin.ai.models.assignToGroup. Key unlock, model quota, and mailbox access remain separate requirements. Do not change the tenant default merely to grant one user access.