SitecoreAI Agentic Studio, explained: agents, flows and governance

Agentic Studio is the part of SitecoreAI where marketers design, customize and manage AI agents. Sitecore launched it with SitecoreAI at Symposium in November 2025, and it has changed almost every month since. This is a plain-English guide to what it is today, what ships in the box, how the controls work, and what a bilingual Arabic and English team should settle before switching agents on.

What Agentic Studio is, and what it is not

Agentic Studio sits inside Sitecore Studio, the extensibility layer of SitecoreAI, next to App Studio (where developers and partners build apps, extensions and agents), the Marketplace (SitecoreAI’s app store) and Sitecore Connect (an add-on for third-party integration). It is where marketing work gets done by agents, with people approving what matters.

It is not a marketer in a box. Sitecore’s own documentation says it plainly: by default, agents do not understand your company’s tone of voice, brand guidelines or business context. That knowledge comes from brand kits and Sitecore Stream, which must be enabled in the Sitecore Cloud Portal. Skip that step and you get fluent, generic content that sounds like everyone else.

The building blocks

  • Standard agents. Conversational agents that decide how to perform a task from their instructions and the tools you give them.
  • Workflow agents. Custom agents built for structured, repeatable, multi-step work, the kind you want done the same way every time.
  • Skills. Packaged capabilities containing instructions, reference files, schemas and scripts, which agents can reuse.
  • Flows. Coordinated sequences of AI-driven and human-assisted steps, such as a campaign built from a brief through to approved assets.
  • Signals. AI-generated market insights on the topics and industries you choose to track.
  • Tools and connectors. Agents act through tools: Pages (create pages, add components, search, take screenshots), Personalization (create variants and manage conditions) and the Marketer MCP for analytics, audiences and campaigns. Since May 2026 you can add your own tools through custom MCP connectors with OAuth-based authentication.

Marketers do not have to leave the editor to use any of this. Since May 2026, Agentic Studio chat and agents open directly from Page builder through the AI icon in the toolbar.

What ships in the box

Sitecore’s marketing describes more than 20 pre-built agents. The documentation lists 17 agents and three flows. Grouped by job:

  • Research and insight: Researcher, Market signals, Competitor analyzer, AEO/SEO researcher, Audience summary and Account data enricher.
  • Content creation: Content generator, Blog writer, Email writer, Brief generator, Bulk content generator (multiple audiences and channels at the same time) and Snackable content generator (long-form content turned into short pieces).
  • Content operations: Translator (which keeps your brand’s tone), Summarizer, Quote extractor, Structured content extractor and Persona content auditor.
  • Flows: ABM campaign, Adaptive optimization (improving content performance from analytics) and Context-aware content.

The controls that make it safe to use

Governance is where Agentic Studio earns its place in a regulated organization. The platform gives you:

  • Approval steps. An Approval action pauses a workflow until a person reviews and approves it. A flow built without review steps runs without review steps, so design them in from the start.
  • A review card in chat. Since July 2026, AI-proposed changes arrive on a review card that gives you full control over what gets saved. Execute mode runs a task directly, subject to your approval policy.
  • Roles and licences. Users are either User or Editor, and a Builder licence is required to create custom agents.
  • Visibility and tools. Admins can make agents private, public or shared with specific people, and switch individual tools on or off.
  • An undo button. The Jobs tool shows what an agent did, and lets you revert its operations.
  • Your data stays yours. Sitecore states that it does not use prompts or results to train models.

What it costs

Sitecore says SitecoreAI customers get full access to Agentic Studio at no additional cost, and its marketing promises no token limits. Five Builder licences are included by default, and more can be bought. In practice the cost of Agentic Studio is people and governance: brand kits, approvers and the time to tune agents to your voice.

Arabic and English

Two recent features matter most for bilingual teams. Brand kits now have a glossary section (April 2026), where you define approved translations for key terms and stop brand, product and campaign names from being translated. Brand-aware translation needs a brand kit assigned to the site. Agents can also run across parameters such as languages and produce an output for each combination.

What the documentation does not yet cover is Arabic itself: output quality, register and right-to-left rendering are not documented. So pilot before you scale. Decide whether you write in Modern Standard Arabic or a Gulf register, have native editors review every Arabic output in the pilot, and keep legal and regulated claims out of machine translation altogether. Our view of what parity takes is in Arabic-first on Sitecore.

Data residency in the Gulf

In February 2026 Sitecore announced dedicated SitecoreAI deployments for the region: delivery from Saudi Arabia’s Eastern Province starting in Q4 2026, and a sovereign instance running locally in the United Arab Emirates, planned for later in 2026. Sitecore has not documented whether AI processing for agents runs in-region. Until it does, agree with your legal team which data may never go into a prompt (personal, banking and health data are the usual starting list), and ask Sitecore and your partner to confirm processing locations in writing.

Where to start: a 90-day pilot

  1. Weeks 1 to 2: foundations. Build Arabic and English brand kits, fill the glossary, assign the five Builder licences, set roles and switch on only the tools the pilot needs.
  2. Weeks 3 to 6: three agents and one flow. Pick low-risk, high-volume work. Summarizer or Snackable content generator on existing articles, Translator with the glossary and native review, and AEO/SEO researcher on your top pages. Add one workflow agent with an Approval step.
  3. Weeks 7 to 12: measure, then widen. Compare against baselines you set on day one: time to publish in both languages, rework after review, and edits to translated copy. Expand only what beats the baseline.

Governance checklist

  • Who holds the Builder licences, and who is an Editor rather than a User?
  • Who approves an agent or skill before it becomes public?
  • Where does every workflow need an Approval step, and who are the named Arabic and English approvers?
  • What approval policy applies to Execute mode in chat?
  • Do we need one brand kit per language or market, and is the glossary complete?
  • Which content is written natively in Arabic, and which may be translated?
  • Which tools and MCP connectors are switched on, and who reviews each one?
  • What data is banned from prompts, and do residency rules mean waiting for the in-region deployments?
  • Who monitors Jobs, who may revert operations, and where is approval evidence kept?
  • Is every agent documented with an owner, a purpose, the data it touches and an approval date?

Frequently asked questions

Does Agentic Studio cost extra?

Sitecore says SitecoreAI includes full access to Agentic Studio at no additional cost, with five Builder licences by default. Additional Builder licences can be purchased.

Can agents publish without a person approving?

They can if you let them. Approval steps, the chat review card and approval policies exist so you do not have to. Build approvals into every flow that touches live content.

Does it support Arabic?

Translation, glossaries and per-language generation are documented. Arabic-specific quality and right-to-left behaviour are not, so treat Arabic as a pilot with native review before you rely on it.

Can we use our own AI assistants with SitecoreAI?

Yes. Sitecore’s Marketer MCP gives AI assistants such as Claude, Copilot Studio and Cursor secure access to SitecoreAI marketing tools, and every action follows Sitecore’s security, permissions and approval workflows.

Where can we see it in person?

Sitecore Symposium 2026 in Orlando (10 to 12 November) has a track on orchestrating experiences with agents, and a SitecoreAI Agent Builder Workshop in the pre-conference training, which costs extra. Our CEO will be there.

Planning your first agents? We set up brand kits, approvals and the pilot as part of Arcsen Ascend, or start with the free Sitecore health check.

Sources

Tags

What do you think?

Related articles