Your Gradial organization must be provisioned before you can begin. Contact your Gradial onboarding manager to initiate provisioning. While you wait, you can complete the discovery prep and security review steps in Phase 1 independently.
Phase 1: Environment Discovery
Gradial leads structured discovery to understand your technology environment, content workflows, and use case priorities. Several steps in this phase can be started on your own before any sessions are scheduled.Prepare your program inputs (start now)
You can complete this step independently, before discovery sessions begin. Gather:
- Key business objectives and success metrics for the engagement
- A sample of example tickets by type (small content updates, large updates, new page requests) — or an export from your ticketing system
- Workflow documentation for your current content process
- Examples of golden template or reference pages
Initiate security review (start now)
Your IT or security team may need to review and approve Gradial’s integration model before any system connections can be made. This is often the longest step in onboarding and is entirely driven by your organization’s internal processes — start it as early as possible.Your Gradial onboarding manager can provide security documentation, architecture diagrams, and compliance information to support this review.
Pre-Configuration: What to Collect Before Setup
Before connecting your systems in Phase 2, your team needs to gather the technical details that Gradial requires to operate correctly in your environment. Collecting these upfront — ideally in a shared document — prevents back-and-forth during setup and helps your IT team submit a single, complete credential request. The six categories below cover everything you’ll need. Use these as a checklist to work through with your CMS admin, MarTech lead, and IT team before your Phase 2 sessions begin.1. Integration Paths
1. Integration Paths
One row per system you’re connecting. This is what your Gradial onboarding manager will need to configure each integration.
What to confirm: The correct author/API endpoint URL for each environment (sandbox vs. production), the authentication method required, and whether IP allowlisting is needed.
| # | Platform | Endpoint / Connection URL | Status | Notes |
|---|---|---|---|---|
| 1 | AEM Sites + Assets | e.g., https://author.yoursite.com | Auth method (OAuth, service account) | |
| 2 | Jira | e.g., https://yourorg.atlassian.net | API token or service account credentials | |
| 3 | Workfront | e.g., https://yourorg.my.workfront.com | WT / Service Account | |
| 4 | Marketo | e.g., https://xxx-EOX-xxx.mktorest.com | REST API — OAuth 2.0 Client Credentials | |
| 5 | SFMC | e.g., https://mcXXX.auth.marketingcloudapis.com | OAuth 2.0 Client Credentials |
2. Content Paths
2. Content Paths
The CMS paths where Gradial’s agent will be permitted to read and author content. Define one row per content root or DAM root.
What to confirm: Exact JCR paths (AEM) or equivalent content roots for your platform, which paths are in scope for the initial engagement, and any paths that should be explicitly excluded.
| # | Content Path | Content Type | Scope | Platform | Notes |
|---|---|---|---|---|---|
| 1 | /content/your-site/en | Pages | Path & sub-paths | AEM Sites | Site root — agent operates on all child pages |
| 2 | /content/dam/your-brand | Assets | Path & sub-paths | AEM DAM | DAM root — all brand assets stored here |
3. Domain Mapping
3. Domain Mapping
Maps public-facing URLs to their CMS content paths. Gradial uses this to resolve page targets when tasks are submitted with a URL rather than a path.
What to confirm: All environments in scope (sandbox, staging, production) and their corresponding CMS paths, plus any locale or region variations.
| # | Public URL | Content Path | Environment | Locale | Notes |
|---|---|---|---|---|---|
| 1 | https://www.yoursite.com/en | /content/your-site/en | Production | en-US | |
| 2 | https://sandbox.yoursite.com | /content/your-site/en | Sandbox | en-US | No public URL in sandbox — AEM author access only |
4. Templates
4. Templates
The page templates Gradial’s agent will use when creating new pages. One row per template type.
What to confirm: The template paths in your CMS for each page type in scope, which template is the default, and which page types map to which templates.
| # | Template Name | Template Path | Type | Page Types | Notes |
|---|---|---|---|---|---|
| 1 | Content Page | /conf/your-site/settings/wcm/templates/content-page | Default | Content pages, landing pages, campaign pages | Primary template — used when no other template is specified |
5. Golden Page Paths
5. Golden Page Paths
Golden Pages are the reference pages Gradial uses as a quality and structure benchmark for new page creation. One row per page type you want covered.
What to confirm: Which pages your team considers the gold standard for each page type, and that those pages are in a stable, published state accessible to Gradial. See Golden Pages for more.
| # | Page Name | Content Path | Template Used | Purpose | Notes |
|---|---|---|---|---|---|
| 1 | Homepage (Golden) | /content/your-site/en/homepage | Content Page | Brand-standard layout benchmark | Use as structure baseline for all new pages |
| 2 | Campaign Landing Page (Golden) | /content/your-site/en/campaigns/golden-lp | Content Page | Reference for campaign page creation |
6. Reference Page Paths
6. Reference Page Paths
Specific existing pages used as layout or content references for new page creation tasks — distinct from Golden Pages in that these are real in-production examples rather than curated benchmarks.
What to confirm: A representative set of existing pages by page type that the agent can use as copy/structure references when Golden Pages don’t exist yet.
| # | Page Name | Content Path | Public URL | Use Case | Notes |
|---|---|---|---|---|---|
| 1 | Sample Campaign LP | /content/your-site/en/campaigns/sample-campaign | https://www.yoursite.com/en/campaigns/sample | Create new page from reference | Use as layout/content reference for new campaign pages |
Phase 2: Credentials & Access
Connect Gradial to your CMS, ticketing system, and other tools. Once your organization is provisioned (Step 1), every subsequent step in this phase is self-service — follow the linked documentation and complete each integration independently.Gradial provisions your organization (Gradial-led)
Your Gradial onboarding manager creates your organization account and sets your initial admin user. Your admin will receive an invite email once this is complete. All steps below can be completed independently after this point.
Add users to your Gradial organization
Log in at app.gradial.com and invite your team members. Identify your core team early — the admin, product owner, and use case leads who will own Gradial day-to-day. See Manage Team Members and Roles & Permissions.
Set up Single Sign-On (SSO)
Connect Gradial to your identity provider (Microsoft Entra ID, Okta, or custom OIDC) to enable SSO. Recommended for all enterprise teams. See Single Sign-On for step-by-step configuration.
Whitelist Gradial's IP addresses (if required)
If your organization restricts inbound connections by IP, you may need to add Gradial’s IP ranges to your allowlist before integrations can connect. Contact your Gradial onboarding manager for the current IP address list. This is typically handled by your network or security team alongside the credential provisioning in the steps below.
Connect your CMS environments
Connect Gradial to your CMS (e.g. Adobe Experience Manager, Sitecore) so agents can read, author, and publish content. For AEM, two accounts are typically required:
- A technical account — used by Gradial to authenticate with the AEM API
- An authoring account — a user account with write permissions to the content paths agents will work with
Connect your ticketing system
Connect your project management tools — Jira, Workfront, Wrike, or similar — so Gradial agents can receive and execute work directly from your existing workflows. See Connecting to External Ticketing Systems.
Connect Figma (if applicable)
If your team uses Figma for design, connect it using a Personal Access Token (PAT) so agents can source design assets and patterns. See Figma Integration.
Connect your DAM system (if applicable)
If your team uses a DAM, connect it so agents can source and manage assets as part of content workflows. See Digital Asset Management.
Phase 3: Platform Onboarding
Configure Gradial for your environment and run end-to-end use case validation together with your Gradial onboarding manager. Setup steps are self-service; validation is a joint exercise.Set up a sandbox area in your CMS/DAM
Create a dedicated sandbox or testing area within your CMS or DAM. This gives you a safe space to run agents and validate outputs before going live. Refer to your CMS admin for the recommended folder and permission structure, or ask your Gradial onboarding manager for guidance.
Create Golden Pages
Golden Pages are reference pages that Gradial uses as a quality benchmark when creating or updating content. They represent your ideal page structure, component usage, and content standards. Set these up and ensure they are accessible in your CMS. See Golden Pages.
Configure design patterns (if applicable)
If you’re using Gradial for page creation or migration, ingest your design system’s component patterns so agents understand your component library and can assemble pages correctly. See Design Pattern Ingestion.
Configure brand, compliance, and QA rules
Set up the rules that agents apply when generating and reviewing content — brand voice, legal compliance guardrails, and QA criteria. Rules can be created directly in the Rules Manager or by asking the agent. See Rules & Skills.
Validate your use cases (Gradial-led, joint)
Your Gradial onboarding manager will run use case validation sessions with your team — working through each in-scope workflow end-to-end against your real CMS environment. This is a collaborative exercise: your team runs the tasks, your Gradial manager guides the setup and troubleshoots issues together with you.Validation covers the full range of workflows in scope:
- Small content updates (copy, images, links) — see Small Content Updates
- Medium content updates (multi-component or multi-page) — see Medium Content Updates
- New page creation from Golden Pages and design patterns — see New Page Workflow
- QA and accessibility reports — see QA Reports and Accessibility Reports
- Translation/localization workflows, if applicable — see Translation and Localization & MSM Inheritance
Phase 4: Use Case Readiness & Training
Training follows a core-first model: Gradial trains your core team, your core team trains the extended user group — with Gradial available to support along the way.Train your core team (Gradial-led)
Your Gradial onboarding manager leads a dedicated training session with the people who will own Gradial day-to-day: your admin, product owner, and use case leads. This session covers how to run each validated use case, how to write effective prompts, and how to troubleshoot common issues. By the end, your core team is ready to operate independently and train others.Use Navigating the Gradial Platform and Prompting an AI Agent as supporting references.
Core team trains extended users (with Gradial support)
Your core team leads training sessions for authors, designers, and other operational staff. Gradial is available to support these sessions — answering questions, joining for complex use cases, and helping ensure your extended team leaves with the same confidence as your core group. Running these sessions internally builds long-term organizational capability.
Assign named internal owners
Before go-live, designate specific people responsible for:
- Prompt maintenance — keeping prompts up to date as your content needs evolve
- Evaluation management — updating QA evals when brand or compliance requirements change
- Use case evolution — identifying and onboarding new use cases over time
Confirm your support process
Know where to go when you need help:
- Platform issues: Customer Support Portal or [email protected]
- Documentation: You’re already here — bookmark the docs and share with your team
- Onboarding questions: Your Gradial implementation manager remains your first point of contact until formal graduation
Grady’s Graduation
Complete graduation sign-off
Gradial onboarding concludes with a formal graduation sign-off — a review confirming that all in-scope use cases have been validated end-to-end, your team is trained, named owners are in place, and your support model is agreed. Your Gradial contact will guide you through this step.