Learn how to set up and configure Autopilot for your organization, including prerequisites, permissions, and alert integration.
Prerequisites
Before setting up Autopilot, ensure you meet the following requirements:
Feature control manager
You can turn Autopilot on or off for your entire organization using Feature control manager. Only an Organization Manager can edit these settings. After you turn on Autopilot in Feature control manager, you still need to configure it in the AI panel using the steps below.
Admin permissions (for setup)
To give users permission to use Autopilot, a user must be an Organization Manager and Authentication Domain Manager.
Dica
If you don't have these permissions, you'll get the message: "This looks like a job for an admin." Contact your organization manager to enable the agent for you.
User permissions (for access)
To use Autopilot, users must be basic, full, or core users.
To give users permission to use Autopilot, an admin or authentication domain manager must assign users a role that includes these organization-level capabilities:
- Autopilot - Read, other (Ask, Add to Automation)
- New Relic MCP Server - Read
Required opt-ins
In addition to turning on Autopilot in Feature control manager, you must opt into the following:
Dica
Cross account destinations is only required if you want to set up alerts with Autopilot. Without it, Autopilot will remain partially configured.
Set up Autopilot
Use the onboarding flow to automatically set up:
- A system identity to represent the agent
- Required permissions for basic use
- An alert destination
Dica
You can configure only one Autopilot agent per organization.
Importante
What is a system identity? A system identity is a non-human identity that allows the agent to authenticate directly to other services without requiring a user account. System identities are scoped to a single New Relic organization.
To onboard Autopilot:
Go to one.newrelic.com
In the upper right, select Ask AI to open the AI panel. Select the three-dot menu, then select Configure. The same menu also has a What's new option, where you can find release notes.
Under Agents, select Autopilot.
In the Agent name field, enter a name for your agent. The system automatically adds
Autopilot -as a prefix and applies this name to the system identity and access management components.From the dropdown, select the accounts you want the agent to analyze.
Importante
You can add an unlimited number of accounts for Autopilot to analyze. Adding more accounts allows the agent to better identify connections and surface insights across your stack. However, the agent's analysis will be visible to any users with Autopilot interaction access, regardless of their direct access to those accounts.
(Optional) Connect Slack to give Autopilot access to your team's conversations as additional context.
Review the Permissions summary. The system grants Autopilot standard read-only access to your selected accounts.
Importante
Admin users will have the ability to modify the accounts and grants provided to the agent. A reduction in grants from the standard read-only role will limit the telemetry data Autopilot can access, which can result in incomplete analysis, missed anomalies, or degraded root-cause identification capabilities.
Click Add Agent. The system takes a few moments to complete the setup.
Dica
Creating the alert destination does not automatically assign any alert conditions or policies to Autopilot. Refer to Integrate with alerts to configure that.
Dica
If the Configure tab shows "Partially configured" next to Autopilot, open the configuration panel and select Update Agent to complete setup.
Integrate with alerts
Connect Autopilot to your alert workflows so that Autopilot insights are automatically attached to every triggered alert or issue.
Configure alert workflows
Dica
Phased approach recommendation: Start with a small subset of critical or high-priority alert conditions or policies to validate performance and confirm the agent works well for your environment, then expand more broadly. Autopilot allows up to 100 requests per hour per organization, so avoid connecting it to noisy, low-priority alerts that could use up that budget.
To set up Autopilot with alerts:
- Go to one.newrelic.com > All capabilities > Alerts > Issues & Activity > Notification Workflows > Add a workflow.
- In your workflow configuration, under the Notify section, select AI agent.
- Choose the Autopilot destination created during onboarding and click Save message.
Dica
The alert prompt is editable. The Autopilot destination uses a default prompt, "Show me what's wrong, check for root cause, show me health charts." You can edit this prompt freely to focus the analysis on what matters for that workflow.
Once configured, when you open a recently fired alert or issue, you'll automatically see the Autopilot summary for that item.