Documentation index by workflow

Documentation
, , ,
1

Documentation index by workflow

Use this index to quickly find the right guide based on your current task, role, or incident type.

Required access: Public. No account required to read.

Start here (new customers)

  1. Getting started with GrootMade
  2. How to install GrootMade Connect
  3. How to activate your license
  4. How to install plugins and themes from GrootMade Connect

Deployment workflows

  1. How to bulk download and install products
  2. How collections work
  3. How to manage connected websites
  4. How sublicenses work

Account and billing

  1. How billing and subscription management works
  2. How to use wallet and credits
  3. How to manage profile and account preferences

Support and incident response

  1. Troubleshooting failed installs or updates
  2. How to use dashboard history and activity logs
  3. How to use support tickets

Branding and domain operations

  1. How to configure white-label branding and domains

Related guides

  • About the Documentation category
  • Getting started with GrootMade
  • Troubleshooting failed installs or updates

Exact route paths

  • /dashboard
  • /dashboard/licenses
  • /dashboard/sites
  • /dashboard/billing
  • /dashboard/support

Expected UI state after each step

  • Step 1: Customer can identify onboarding guides immediately.
  • Step 2: Deployment-related guides are grouped logically.
  • Step 3: Support/incident guides are easy to find during outages.
  • Step 4: Account and billing guides are clearly separated from operations guides.

Screenshot map (step-level)

  1. Dashboard navigation context

  2. Operational category map

Operational objective

Complete the “Documentation index by workflow” workflow with predictable outcomes, clear auditability, and repeatable execution quality across team members and projects.

Acceptance criteria (all must pass)

  • The workflow can be completed without missing permissions or blocked route access.
  • All required dashboard routes load successfully for the active account.
  • The expected UI states are visible in the same order as documented.
  • At least one end-to-end validation confirms the process works in practice.
  • Evidence artifacts are captured for support and audit handoff.

Routes that must be reachable during validation:

  • /dashboard
  • /dashboard/licenses
  • /dashboard/sites
  • /dashboard/billing
  • /dashboard/support

Failure modes and exact remediation

  • Permission failure: Recheck plan/license entitlements and retry after session refresh.
  • Route loads but action is missing: Confirm feature flags/plan gates and selected context (site/license).
  • Action runs but state does not update: Refresh, re-open the relevant page, and verify from history/log view.
  • Partial success in multi-step operations: Retry only failed sub-steps and preserve successful state.
  • Cross-page mismatch: Reconcile with dashboard history and capture timestamps before escalation.
  • Persistent failure after one controlled retry: Open support ticket with full evidence package.

Evidence package for support escalation

Collect all items before escalating:

  • Account email and user role
  • Affected route path and exact action taken
  • Site URL, product/license identifier (if relevant)
  • Timestamps for first failure and latest retry
  • Expected result vs actual result
  • Screenshot set listed below

Screenshot evidence checklist

  • Step 1: Dashboard navigation context
  • Step 2: Operational category map
  • One screenshot with visible timestamp (system clock/browser tab)
  • One screenshot showing route context or breadcrumb
  • One screenshot showing final persisted result
  • Replace any generic placeholder/demo visuals with real environment captures

FAQ

Can I skip steps if I already know this workflow?

Skip only after all acceptance criteria still pass. If any criterion fails, run the full sequence exactly as documented.

Should I run this in production first?

Use staging first for medium/high-impact changes. Promote to production only after validation evidence is complete.

What if my screen does not match the guide exactly?

UI can vary by plan and feature access. Validate route access, plan gates, and expected state outcomes instead of pixel-perfect layout.

How many retries should I perform before escalation?

Run one controlled retry after checklist validation. If failure persists, escalate with full evidence to avoid hidden side effects.

Who owns this guide operationally?

Customer Success owns this guide and its periodic review cycle.

Guide metadata

  • Difficulty: Beginner
  • Estimated completion time: 5-10 minutes
  • Owner: Customer Success
  • Last reviewed: 2026-03-18