Configuring MCP Settings

The MCP Settings tab controls whether the Wizard Assistant is allowed to act on records in addition to answering questions. By default the Wizard only retrieves information; with MCP settings enabled, you can also let it create, update, or delete records on behalf of the user, strictly within the user's existing security permissions.

Opening the Tab

1. Navigate to Setup > Manage > Community Settings > AI Tools Settings.
2. Select the MCP Settings tab.

Enabling Wizard Actions

1. Toggle Enable Assistant Wizard Actions. When enabled, the Wizard Assistant can perform record actions on behalf of the user, scoped to that user's existing access level.
2. The Access Level and Assistant Record Permissions sections appear once Wizard Actions are enabled.

Setting the Access Level

Choose who is allowed to ask the Wizard Assistant to perform record actions:

• All Users - Every user who has access to the Wizard Assistant can request record actions.
• Specific Roles - Only users in the roles you select can request record actions. When you select Specific Roles, a Roles picklist appears; choose the roles that should be granted action permissions.

Access Level only narrows who can request actions. The user's existing security role still controls which records are visible and editable.

Assistant Record Permissions

The Assistant Record Permissions panel lists the action types the Wizard Assistant is allowed to perform. Each action is independently controlled by a toggle:

• Insert - Allow the Assistant to create new records on entities the user has access to.
• Update - Allow the Assistant to modify existing records that the user has permission to update.
• Delete - Allow the Assistant to delete records that the user has permission to delete.

If the user does not have permission to perform a given action on a given record, the Assistant cannot perform it either - the underlying security model is always enforced.

Saving Your Changes

Click Save at the bottom of the page. Changes apply immediately to the next interaction with the Wizard Assistant.

Use Cases

• Power users updating records through chat. Allow Internal Sales Operations to ask the Wizard things like "Update the close date on opportunity Acme Q3 to next Friday." Faster than navigating to the record for users who manage many records per day.
• Pilot the action capability with a controlled group. Set Access Level to Specific Roles and pick a single role first. Validate the action quality and audit trail before broadening to All Users.
• Read-only Wizard for partners, action-enabled for internal staff. Configure Wizard role assignment to include both partner and internal roles, but set MCP Access Level to Specific Roles with only internal roles selected. Partners get read-only Q&A; internal staff get full action capability.
• Allow Insert and Update without Delete. Reduce risk by enabling create and modify actions but never delete actions through chat.

Troubleshooting

• Symptom: A user is told the Wizard cannot perform an action.
  Cause: The relevant action toggle (Insert, Update, or Delete) is off, or the user is not in an Access-Level-permitted role, or the user's security role does not allow the action on the entity.
  Resolution: Verify the Insert/Update/Delete toggles, verify the user's role is included if Specific Roles is selected, and verify the user's security role permits the action on the target entity.
• Symptom: The Wizard performs an action but on the wrong record.
  Cause: The natural-language reference was ambiguous (for example, multiple opportunities named "Acme").
  Resolution: Encourage users to reference records with unambiguous identifiers (record IDs, full names, or filter context).
• Symptom: Action permissions are saved but a user still cannot perform actions.
  Cause: The user's session predates the change.
  Resolution: Have the user log out and back in.
• Symptom: The Access Level section does not appear.
  Cause: The Enable Assistant Wizard Actions toggle is off.
  Resolution: Toggle Enable Assistant Wizard Actions on first; the Access Level and permissions panels appear immediately.
• Symptom: Audit log does not show Wizard-driven actions distinctly.
  Cause: Wizard-driven actions are recorded as actions by the user themselves (since the Wizard acts on their behalf within their permissions).
  Resolution: Use the conversation history captured by the Wizard for an action audit trail; the underlying record audit reflects the user.

<< Configuring the Wizard Assistant | Using AI Features >>