Configuring the Wizard Agent

The Wizard Agent is the third tab on the Artificial Intelligence Settings page. It controls the action-capable side of the Wizard - letting it create, update, or delete records on behalf of users, and optionally exposing an MCP endpoint so external AI assistants can do the same, all bounded by each user's existing security permissions.

The tab is powered by Magentrix's internal Model Context Protocol (MCP). The tab keeps a section called MCP Settings for admins who need the technical detail, but everything on the tab is configured together.

Opening the Tab

1. Navigate to Setup > Manage > Community Settings > Artificial Intelligence Settings.
2. Select the Wizard Agent tab. A hero banner introduces the feature and a Beta pill signals that the Wizard Agent is currently in beta.

Enabling the Wizard Agent

1. At the top of the tab, toggle the Wizard Agent on. A Kill switch button next to the toggle lets you turn all Wizard Agent access off immediately if needed.
2. Below the hero, two Wizard Agent Capabilities reference cards summarize what the Wizard Agent can do out of the box - grouped as Partner Management and Customer Management, each with its own audience toggle (Partner Manager / Partner Experience, or Customer Manager / Customer Experience). The cards are informational; there is nothing to configure inside them.

MCP Settings

The MCP Settings section controls whether external AI assistants can connect to your portal through the Model Context Protocol. Turn on Enable MCP for External AI Assistants to make the portal's MCP endpoint available to outside tools. Once enabled, the following information appears:

• MCP URL - The endpoint external tools connect to. Read-only, with a copy-to-clipboard button. Share this URL with the developer or vendor of the tool you are connecting.
• Access Token Lifetime (minutes) - How long an issued access token remains valid before a refresh is required. Default 60.
• Refresh Token Lifetime (days) - How long a refresh token remains valid. Default 30.
• Authorization Server Metadata URL - A read-only URL pointing at the standard OAuth 2.1 discovery document (/.well-known/oauth-authorization-server). Tools that support RFC 8414 can read this to discover the authorization, token, and registration endpoints automatically.

How External Tools Register

Admins do not manually create credentials for external tools. When a tool first connects, it registers itself with the portal automatically (using the OAuth 2.1 Dynamic Client Registration standard, RFC 7591) and receives its own Client ID and Client Secret. On first sign-in, the user sees an authorization screen describing what the tool is requesting:

• Read data through MCP tools (query records, view information) - the mcp:read scope.
• Create, update, and delete data through MCP tools - the mcp:write scope.

The user can Allow Access or Deny. Access tokens are bound to the user's role; the tool can do only what that user is allowed to do, further narrowed by the Access Level and Assistant Record Permissions you configure below.

Registered OAuth Clients

Click the Registered OAuth Clients row to open a drawer listing every external tool that has connected. For each client the drawer shows:

• The tool's name and Client ID.
• The date it was registered.
• The users who have authorized it.
• A Revoke button.

Revoking a client disconnects every user authorized through it and invalidates their tokens immediately. A confirmation dialog ("Revoke OAuth Client") protects against accidental clicks. The tool will need to be re-authorized to connect again.

Who Can Use the Wizard Agent

The Who Can Use the Wizard Agent section controls which users can request record actions.

• All Users - Every user who has Wizard Assistant access can also request Wizard Agent actions.
• Specific Roles - Only users in the roles you select can request actions. When you select Specific Roles, a Roles picklist appears; choose the roles that should have action capability.

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 Agent is allowed to perform. Each action is independently controlled by a toggle:

• Insert - Allow the Assistant to create new records to entities 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.

Above the toggles, the panel shows an Applies to line that mirrors your Access Level choice - either Applies to: All Users or Applies to Roles: followed by the selected role names. If the user does not have permission to perform a given action on a given record, the Wizard Agent cannot perform it either - the underlying security model is always enforced.

Saving Your Changes

The Artificial Intelligence Settings page uses a single Save button at the bottom that commits changes across all three tabs. Click Save after configuring the Wizard Agent - a Settings saved successfully! toast confirms the save. Changes apply immediately to the next interaction with the Wizard Agent.

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 the Wizard Assistant to include both partner and internal roles, but set the Wizard Agent 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.
• Connecting an external AI assistant. Enable MCP for External AI Assistants, share the MCP URL with the tool's vendor, and review the Registered OAuth Clients drawer once the tool connects and users authorize it.

Troubleshooting

• Symptom: The Wizard Agent tab shows a "Wizard Assistant is disabled" warning.
  Cause: The Wizard Assistant master toggle on the second tab is off. The Wizard Agent requires it to be on.
  Resolution: Open the Wizard Assistant tab, enable the assistant, save, then return to the Wizard Agent tab.
• Symptom: A user is told the Wizard Agent 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 Agent 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 MCP URL and token lifetime fields do not appear.
  Cause: The Enable MCP for External AI Assistants toggle is off.
  Resolution: Turn it on to reveal the endpoint details. External tools cannot connect while the toggle is off.
• Symptom: An external tool is behaving unexpectedly and should be disconnected.
  Cause: The tool needs its OAuth credentials revoked.
  Resolution: Open the Registered OAuth Clients drawer, find the client, and click Revoke. All tokens for that client are invalidated 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 >>