Manage Ask Yarken settings and AI Studio features

Use this guide to find the settings that control Ask Yarken, AI action cards, Copilots, and other AI Studio features. General environment settings and AI Studio configuration are in separate areas.

Where to configure AI features

Enable Ask Yarken

1. Open Admin > Settings > AI > Ask Yarken.

2. Review Enable Ask Yarken and the available feature controls for your environment.

3. Where your AI Studio environment uses Ask Yarken Beta, enable it as required for eligible administrators.

4. Save your changes and verify that an eligible user can open Ask Yarken from the top navigation.

See Ask Yarken (Admin Settings) for attachment settings, Beta access, and availability details.

Add organization context

Organization context for Ask Yarken provides concise guidance for interpreting your organization's terms and financial policies. Use it for company-specific definitions, reporting conventions, or answer preferences.

Example: Use the approved fiscal calendar. When explaining forecast variances, show the affected period, amount, and supporting drivers. State when the available data cannot explain the difference.

Organization context does not override user permissions, configured financial data, or source-backed results.

Manage conversation context

Use Ask Yarken: Max conversation context to control how much conversation history Ask Yarken carries into each new question before summarizing older messages.

Choose 100k tokens for the recommended context setting, or 150k tokens when you need more earlier conversation detail at a higher cost.

For configuration steps and more information, see Ask Yarken (Admin Settings).

Control ambiguous name matches

Ask Yarken may find multiple matches for a vendor, account, application, or cost centre mentioned in a question. In Search lookup: Ambiguous matches, choose how these cases are handled.

When names or master data change, open Admin > Settings > AI > Lookup Search to review dimension indexing.

Configure AI actions and Copilots

Action Types define what Automations can raise for review, including the shape of the finding, payload fields, impact, default recipient, and fields used to identify repeated findings. See Configure AI Action Types.

Copilots are configured under AI Studio. Enable or disable the relevant Copilot and save settings. See Enable and configure AI Studio Copilots.

Set up an action from start to finish

1. Create or import Action Type in Admin > Settings > AI > Action Types.

2. Configure producing Automation using Raise an action and map its required contract fields.

3. Create a separate follow-up Automation using On app event > An action is accepted; choose Action Types handled by this workflow.

4. Test action card in Inbox, select Act on this, and review follow-up Run History.

Use Wait for approval before follow-up steps requiring authorization. Action acceptance does not approve subsequent changes. See Configure AI Action Types and Review findings with Take Action.

Check a configuration change

• Confirm the feature is enabled and the user has the required licence and role.

• Test a representative Ask Yarken question, Copilot action, or Automation run.

• Check the selected dimension values, data permissions, and source results.

• For Automation failures, inspect Run History. For missing or repeated actions, check Action Type field mappings and Lifecycle settings.

Related content

• AI Studio - Complete Guide

• AI settings

• AI Studio - Knowledge Base