Breadcrumbs

Enable and configure AI Studio Copilots

Copilots control contextual AI experiences across supported Yarken screens.

Example: Make graph explanations follow finance terminology

Scenario: Finance users want graph summaries to follow organization’s naming and present variance figures consistently.

  1. Open Graph Explanation Copilot settings and verify enabled.

  2. In Graph Explanation Context, define approved metric definitions, preferred terminology, and required explanation structure.

  3. For example: mention chart date range and units, describe highest and lowest values, provide up to three evidence-based observations, and label unverified drivers as hypotheses.

  4. Save settings, invoke Copilot on supported chart, and verify wording against actual values. Context should not instruct model to fabricate figures.

Open Copilot settings

  1. Go to Admin > AI Studio > Channels > Copilots.

  2. Find Copilot card.

  3. Select settings icon.

  4. Enable or disable Copilot for all users using toggle.

  5. Select Save.

Copilots shown

  • Costpool Rules Copilot: Assist with cost-pool mapping rules.

  • Costpool Mapping Copilot: Assist with cost-pool mapping.

  • Tower Mapping Copilot: Map cost-pool spend to towers and distribute to assets or solution offerings.

  • Tower Rules Copilot: Assist with tower mapping rules.

  • Dashboard AI Narrative: Generate narratives and summaries for dashboard widgets and reports.

  • Take Action: Presents assigned findings from Automations configured to raise actions. Configure finding types and ownership under Admin > Settings > AI > Action Types.

  • Graph Explanation Copilot: Explain dashboard chart and graph data.

Some mapping Copilots display Beta status. Availability varies by environment.

Graph Explanation Context

  1. Open Graph Explanation Copilot settings.

  2. Enable Copilot.

  3. In Graph Explanation Context, enter organization-specific guidance for explanation style, relevant definitions, or output format.

  4. Save.

  5. Open supported graph, invoke Copilot, and verify explanation follows expected context.

Keep context specific. Review generated recommendations against underlying graph data.

Take Action and Action Types

Use Admin > Settings > AI > Action Types to define finding shape, required facts, impact value, ownership and lifecycle. Raise an action in Automation Builder produces findings. Take Action presents findings produced by Automations. When an acceptance handler is configured, recipient can start follow-up workflow.

Accepting finding is different from approving changes. Handler must include its own approval gate before consequential writes.

See Review findings with Take Action and Configure AI Action Types.