Manage saved searches from chat

Open Complexity, select your own mailbox, and enable the required saved-search tools. Each needs a separate group grant. Every call checks current actor rights and a MailGen license, then resolves the owned mailbox.

mail.read and at least one engine permission, mail.finderSQL or mail.finderOpenSearch, are required. Retrying an engine also needs that engine's permission.

Tool	Purpose
listOwnSavedSearches	Pages through your saved definitions.
getOwnSavedSearch	Reads one definition.
createOwnSavedSearch	Saves an existing owned search run with a name.
updateOwnSavedSearch	Renames an existing saved search.
rerunOwnSavedSearch	Starts a new run from the saved definition.
retryOwnSearchRun	Retries the selected engine for an owned run.
readOwnSearchPreferences	Reads the mailbox's stale-result preference.
updateOwnSearchPreferences	Sets staleAfterHours to a positive integer through 2147483647, or null.
deleteOwnSavedSearch	Proposes deletion through a separate approval flow.

These use the search services behind /api/saved-searches, /api/searches, and /api/searches/preferences. The server supplies mailboxUserId to IUDG and DataSearcher. The model cannot supply another user or account. Create, rename, rerun, and retry retain backend owner checks.

Write request IDs derive from runId, toolCallId, and tool name. Repeating the same call is idempotent. An accepted rerun is not a complete result set. Inspect engine progress before using partial results.

Deletion is available through saved-search deletion approval. It removes a definition and retires runs, not messages.