AI and Assistant settings

/ai/settings contains the AI module and Assistant settings. Rights are checked per card and action: without view access a section is hidden; with view but no manage access its fields are read-only.

AI module settings

The AI card lets you enable the module, allow images, and set visible input, output, and context limits, timeout, and result format. Some values may be read-only; change only fields exposed by the form.

Module limits are the upper bound for Playground and scenarios. After changing them, test long input, JSON output, timeout, and “Reject”/“Truncate” behavior. Allowing images does not grant access to every file: choose the source explicitly.

Assistant module and profiles

In Assistant, select a profile, default scenario, and processing mode when those controls are visible. Profiles are updated from the list and form; leave values unchanged when the current screen does not provide a control.

A profile links a connection and scenario. Its switches control access to tasks, CRM, and images, along with the action limit. These settings describe the profile and do not expand the user’s rights.

Replies and actions are different

Reply and action rights are assigned separately in portal access settings (/portal-settings?tab=policies). Do not enable CRM write just to prepare a draft.

Review and safety

Review the profile owner, scenarios, action limit, and processing mode. Never expose keys, internal addresses, prompts with personal data, or amounts. Before enabling a profile, check that action and message names use the portal’s selected language.

If part of a section does not load, AI Hub should clearly name the missing data instead of treating it as zero. Refresh repeats the settings, connections, scenarios, and profile load; rights change only in access settings.

Related: AI Playground, AI scenarios, AI connections, Portal administration.