February 2026
Chats
- Ask questions about Gradial features, best practices, and your existing content
- Get answers grounded in your documentation and real-time web research
- Create new tasks directly from chat. The agent routes them to the correct workspace and environment.
- Find and resume past conversations in the Chats tab in the sidebar
Cmd+J from anywhere to start a conversation.Google Analytics Integration
Connect your Google Analytics 4 properties directly to Gradial. Once linked, your AI agents can query traffic, engagement, and conversion data on demand — no manual exports or dashboards required.What you can do:- Pull metrics like active users, bounce rate, session duration, and conversion rate across any date range
- Break data down by dimensions such as traffic source, device, country, or page path
- Let agents reference real performance data when making content recommendations
External Web Search Across All Gradial Agents
We’ve added built‑in external web search to Gradial so every agent can pull in fresh, relevant context without leaving your workflow. This means you can ask open‑ended questions, validate claims, and ground your content in current sources directly inside chat.
External Web Search is now available across all Gradial agents, including Sitecore, AEM, Thread Orchestrator, and Batch mode, with a clear in‑chat “search in progress” state and a clean list of results for quick review.
What This Enables
- Get fast answers to exploratory questions backed by real web results
- Validate facts and references before drafting content
- Discover competitor positioning, market trends, and benchmarks in minutes
- Bring credible external context into AEM and Sitecore workflows
- Stay in flow: research and execution now happen in the same place
Example Prompts
- “Find the latest enterprise CX benchmarks and summarize the top three trends.”
- “Research competitor messaging on AI-assisted content tools and draft a comparison outline.”
- “Look up current best practices for AEM asset tagging and suggest a checklist.”
- “Search for recent product launch messaging in our category and propose 3 angles.”
Design System Collections
Design systems in Gradial are powerful to create consistent content. But as they grow, finding and reusing the right patterns can become harder. That’s why we’re introducing Collections.
- Design System → your complete pattern library
- Collections → flexible, purpose-built subsets of that library
- Blog pages
- Marketing campaigns
- Product flows
Where to Find Collections
Collections live directly inside your design system.You’ll see them on your Design System page in a dedicated Collections tab, making it easy to browse and manage all your curated sets in one place.To get started, click Create Collection to open a modal where you can build a new Collection. Every Collection you create will appear in this tab.
- Add, remove, or update patterns in a Collection
- Edit tags and metadata
- Refine Collections as your work evolves
Manage Design Systems & Collections Per Workspace
Gradial design systems help teams create consistent, reusable content at scale. But as organizations grow, not every workspace needs access to every pattern library.That’s why we’re introducing workspace-level scoping for design systems and collections.Now, teams can control exactly which design systems, and which collections within them, are available for each workspace.
Workspace Settings → Design Systems Tab
A new Design Systems tab is now available in Workspace Settings.From here, you can:- Associate one or more design systems with a workspace
- Scope access further by selecting specific Collections within a design system
- Quickly jump into details with View Patterns
Smart Filtering Based on Your AEM Environment
Gradial automatically ensures that only relevant design systems appear for selection.Design systems are filtered based on your workspace’s AEM integration URL, so you’ll only see systems that contain patterns ingested from the same AEM instance.That means:- No clutter from unrelated environments
- No accidental cross-instance confusion
- Only the design systems that apply to your workspace
Pattern Inheritance for Child Tasks
When working with batches, campaigns, or folders, customers often need the same patterns applied across all child tasks. Previously, pattern selections had to be configured individually for each task — a tedious process that didn’t scale.To solve this, we’re rolling out Pattern Inheritance: pattern selections now automatically flow from parent to child tasks.
How It Works
When you select patterns on a parent task (batch, campaign, folder, or migration), those patterns are automatically inherited by any child tasks created under it.- Select patterns once at the parent level
- All new child tasks inherit those selections automatically
- No manual configuration needed for individual tasks
- Manually through the UI
- Via Excel/CSV uploads
- By the agent during task execution
Inheritance Is a Snapshot
Pattern inheritance captures the parent’s selections at the moment each child is created:- Children get the parent’s current pattern selections when created
- Existing children keep their selections (inheritance won’t override)
- You can still customize individual child tasks after creation
Pattern Selections Persist Across Sessions
As part of this update, pattern selections are now saved to task history. When you return to a task:- Your previous pattern selections are automatically restored
- The sidebar shows which patterns were selected
- No need to remember or re-select patterns each time
Benefits
- Set once, apply everywhere — Configure patterns at the parent level and let inheritance do the work
- Faster batch setup — No more selecting patterns for each individual task
- Consistent output — Ensure all child tasks use the same patterns for uniform results
- Flexible overrides — Still customize individual tasks when needed
Draft Patterns
As design systems grow across the organization, users need the flexibility to control which patterns are available to the authoring agent. Whether it’s hiding work-in-progress patterns or temporarily removing patterns that need refinement, teams need a simple way to manage pattern visibility.To solve this, we’re rolling out Draft Patterns: a way to control which patterns the authoring agent can use.
Patterns Are Now “Released” by Default
When new patterns are added to a design system, they’re immediately available for the authoring agent to use. No extra steps required — patterns work out of the box.This means faster onboarding and less friction when expanding a design system.New “Draft” Status for Patterns
The pattern detail panel now includes a Status dropdown, which shows whether a pattern is:- Released — actively available to the authoring agent when running tasks
- Draft — stored in the system but hidden from the authoring agent
- It remains fully visible and editable in the Design System admin
- It shows a clear “Draft” badge in the patterns list
- It will not appear in the authoring agent’s pattern registry
- The agent cannot use it when generating content
- Work-in-progress patterns that aren’t ready for production
- Patterns that need refinement before being used
- Temporarily hiding patterns without deleting them
How to Change Pattern Status
- Navigate to Design Systems in the admin
- Select the design system and open the Patterns list
- Click on any pattern to open its detail panel
- Use the Status dropdown to toggle between “Released” and “Draft”
Benefits
- Faster onboarding — New patterns work immediately without manual activation
- Quality control — Keep work-in-progress patterns hidden until they’re ready
- Flexibility — Easily show or hide patterns as customer needs evolve
- Non-destructive — No need to delete patterns; just set them to Draft and re-enable later
January 2026
Configure multiple identity providers for a single organization
Gradial now supports multiple SSO configurations for a single organization—useful for organizations spanning multiple geographies with separate identity providers, or when a managed service provider is supporting your implementation.To add additional SSO connections, repeat the setup steps for each identity provider in Settings → Integrations → Single Sign-On.See our SSO documentation for setup instructions.
Updated Ticket UI
We’ve redesigned the ticket interface to improve clarity when working with tasks.Properties Above Task RequestTask properties (status, priority, approver, workspace, and actions) now appear prominently above the task request section. This layout gives you immediate context about the ticket’s state without clicking. Long ticket requests will also appear inline without the need to scroll through a container.
