> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gradial.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How Gradial Works

> The mental model behind Gradial: how agents receive work, execute it across your stack, and get smarter about your organization over time.

Gradial's operating model can be summarized in three words:

<CardGroup cols={3}>
  <Card title="Assign the work" icon="inbox">
    Work comes in from wherever it originates — Gradial's interface, a Jira ticket, a Workfront task, a brief or work request. No change to how you initiate work.
  </Card>

  <Card title="Agents execute" icon="bolt">
    Agents read the task, understand the intent, and execute end-to-end across connected systems — without manual handoffs between tools.
  </Card>

  <Card title="Governance is automatic" icon="shield-check">
    Every output is checked against brand, accessibility, compliance, and QA rules the organization has defined — on every task, every time.
  </Card>
</CardGroup>

Everything about how Gradial works flows from this model.

***

## The Anatomy of a Task

To make this concrete, here is what a single task lifecycle looks like:

<Steps>
  <Step title="Task created">
    Via Gradial's interface, a connected ticketing system (Jira, Workfront, Wrike), or a brief or work request document. Work can also be pre-scheduled and queued with dependencies set in advance.
  </Step>

  <Step title="Agent picks up the task">
    Reads the description, identifies the target content, and determines which systems are involved.
  </Step>

  <Step title="Agent retrieves context">
    Pulls relevant assets from the DAM, references brand rules and guidelines, checks templates and content patterns for the relevant page type.
  </Step>

  <Step title="Agent executes the work">
    Authors, updates, tags, builds, or publishes as specified — navigating connected systems the way a skilled team member would.
  </Step>

  <Step title="Governance runs automatically">
    QA, accessibility (WCAG 2.2 AA), brand, and compliance checks are applied to the output before it reaches a human reviewer.
  </Step>

  <Step title="Output is reviewed">
    The team reviews at whatever level of oversight is configured — full review, spot-check, or auto-approve for trusted task types.
  </Step>

  <Step title="Task completed">
    Status updated across connected systems. Audit trail created. Follow-on tasks triggered if needed.
  </Step>
</Steps>

This cycle takes minutes for a standard content update. For bulk operations — updating hundreds of pages across a site — the same cycle runs in parallel across all items simultaneously.

***

## The Jobs Gradial Does

You don't pick an agent. You describe the job, and Grady does it — drawing on the right expertise and the right connected systems for the work in front of him. What follows is the range of jobs teams hand to Gradial, not a menu you have to choose from.

<CardGroup cols={2}>
  <Card title="Update content that's already live" icon="pen-to-square" href="/docs/updating-existing-experiences-i-e-content-updates/content-updates">
    A headline, a CTA, an expired offer, a legal phrase across every regional homepage. From a single field to hundreds of pages, inside your CMS's own component structures and publishing rules.
  </Card>

  <Card title="Build something new" icon="file-circle-plus" href="/docs/creating-new-experiences/new-page">
    Landing pages, product pages, campaign hubs — built from a Figma file, a Word brief, a reference URL, or a prompt, using the patterns your site already uses.
  </Card>

  <Card title="Make assets findable and usable" icon="images" href="/docs/asset-management/digital-asset-management">
    Ingest a campaign delivery, tag it against your real metadata schema, carry rights and campaign context over from the job ticket, and retrieve the right asset when another job needs it.
  </Card>

  <Card title="Check the work before anyone sees it" icon="magnifying-glass-check" href="/docs/quality-assurance-and-accessibility/qa-report">
    Brand accuracy, accessibility, legal and regulatory language, and your own custom criteria — applied to every output, not to a sample.
  </Card>

  <Card title="Build and send the campaign" icon="envelope" href="/docs/campaign-management/crm-email">
    Emails, templates, variants, journeys and audiences in your marketing platform — with the same brand and compliance checks used on web content.
  </Card>

  <Card title="Turn a brief into executed work" icon="list-check" href="/docs/campaign-management/cross-channel-campaigns">
    One campaign brief becomes every deliverable it implies, across every channel it touches, with dependencies sequenced and review gates in the right places.
  </Card>

  <Card title="Localize for every market" icon="language" href="/docs/translation-and-localization/translation">
    Translate pages, assets and video in place — respecting inheritance and regional rules — without exports or file handoffs.
  </Card>

  <Card title="Find out what's working, then fix it" icon="chart-line" href="/docs/insights/geo">
    AI-search visibility, CX journey audits, SEO and analytics — and then the content changes that act on what they surface.
  </Card>
</CardGroup>

### One job, many systems

Most real work spans several of the jobs above and several of your systems. Gradial sequences that automatically — running in parallel what can run in parallel, holding what has to wait, and passing outputs between steps without a handoff.

<Info>
  **Example: launch a localized campaign landing page in three markets**

  1. The brief is read and broken into work: one page build, three localized variants, QA on all four, and the assets each one needs
  2. The primary page is built from the Figma reference
  3. Required assets are retrieved from the DAM, rights-checked and tagged
  4. Three regional variants are created
  5. Brand, accessibility and compliance checks run across all four pages
  6. Status is logged back to your work management system and the team is notified for review

  What would typically require coordination across multiple tools, teams and handoffs is **one job** in Gradial.
</Info>

***

## How Gradial Connects to Your Stack

Gradial is integration-first by design. A task that requires finding an asset, updating a CMS page, running a QA check, and logging the completion in a ticketing system is **one task** in Gradial — not four separate steps across four separate tools.

| Category | Supported platforms |
| - | - |
| **Content management** | Adobe AEM (6.5 and Cloud Service), SitecoreAI CMS (XM Cloud), Sitecore XP, Contentful, Contentstack, Sanity, Drupal, WordPress, Gradial ACI |
| **Digital asset management** | AEM Assets, Bynder, Sitecore Content Hub, Aprimo, Box, SharePoint, Google Drive |
| **Work management & ticketing** | Jira, Workfront, Wrike, Asana, monday.com, Azure DevOps |
| **Email & marketing automation** | Marketo, Salesforce Marketing Cloud, HubSpot, Braze, Airship, MoEngage, SendGrid |
| **CRM** | Salesforce CRM |
| **Audiences & journeys** | Adobe Experience Platform, Adobe Journey Optimizer, Adobe Target |
| **Paid media** | Google Ads, LinkedIn Ads, Reddit Ads |
| **Social** | LinkedIn, X |
| **Commerce** | Shopify, Salesforce B2C Commerce |
| **Creative & DCO** | Figma, DaVinci Commerce (Jivox) |
| **Analytics** | Adobe Analytics, GA4, Adobe Customer Journey Analytics, Google Search Console |
| **Productivity & collaboration** | SharePoint, Box, Google Drive, Slack, Word, Excel, PowerPoint |
| **Custom** | Your own REST API via its OpenAPI spec, or a secure MCP server — connect internal knowledge bases, proprietary data systems, or custom AI context layers |

Integrations are configured once during implementation. Once in place, they're available to every user and every job in the workspace — no per-task configuration required.

<Note>
  Availability varies by plan, and not every integration is enabled for every organization by default. The [Integrations Overview](/docs/integrations-administration-and-setup/integrations/get-started-with-integrations) lists what's currently set up for you; your Gradial team can confirm what's available on your plan.
</Note>

[See full integration setup documentation →](/docs/integrations-administration-and-setup/integrations/get-started-with-integrations)

***

## Brand Intelligence — How Gradial Gets Smarter Over Time

An agent that can execute work is only as good as its understanding of what *good* looks like for a specific organization. Generic AI outputs are not enterprise outputs.

This is the brand intelligence layer: the encoded knowledge of how your brand sounds, how your content is structured, what your compliance requirements actually mean in practice, and how your team operates. Gradial builds this intelligence from the standards you configure and the work agents do — and applies it on every task, automatically.

Gradial builds organizational brand intelligence across four areas:

<AccordionGroup>
  <Accordion title="Brand voice and editorial standards" icon="book-open">
    Organizations bring their brand guidelines, tone documents, and editorial standards into Gradial. Agents reference these on every content task. Over time, as agents complete more tasks and teams review outputs, the platform develops a working understanding of what on-brand actually means in practice — beyond what a style guide alone can capture.
  </Accordion>

  <Accordion title="Quality and compliance thresholds" icon="circle-check">
    What passes a QA check at a financial services company is different from what passes at a consumer brand. Gradial learns an organization's specific QA criteria — accessibility standards, regulatory language requirements, brand accuracy rules, custom checks — and applies them consistently. As those thresholds evolve, Gradial evolves with them.
  </Accordion>

  <Accordion title="Content patterns and structural preferences" icon="table-columns">
    Organizations develop patterns over time — how pages are structured, how assets are named, how campaigns are briefed. Gradial learns these patterns and applies them, so agents produce outputs that fit naturally into the existing environment rather than requiring extensive post-processing.
  </Accordion>

  <Accordion title="Workflow and team preferences" icon="arrows-split-up-and-left">
    Some teams prefer agents to draft for review; others want agents to publish directly for certain task types. Some route approvals through specific channels; others use automated sign-off for routine work. Gradial learns these preferences and adjusts how it handles work accordingly.
  </Accordion>
</AccordionGroup>

### The progression most teams follow

| Stage | What it looks like |
| - | - |
| **Early** | Agents execute with frequent human review. The platform is calibrating to the organization's standards. Every review is input. |
| **Established** | Agents handle a wider range of tasks with lighter oversight. Outputs consistently meet the bar for common task types. Human review shifts toward edge cases. |
| **Advanced** | Agents operate with high autonomy on routine jobs. Teams focus on directing outcomes, not reviewing execution. |

The pace of this progression varies. Some teams move through all three stages in weeks; others take longer. The level of autonomy is always in the team's control.

***

<Tip>
  Ready to go deeper? [Request a demo](https://www.gradial.com/request-demo) to see agents running against your actual CMS and content, or [navigate the platform →](/docs/getting-started/navigating-the-platform) to see how these concepts map to the Gradial interface.
</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.