About the Documentation category

Documentation
, ,
1

About the Documentation category

This category contains practical, step-by-step guides for customers using licenses, sites, installs, collections, sublicenses, and billing in GrootMade.

Required access: Public. No account required to read.

How to use this documentation

Use this category like an operations playbook.

  1. Start with the Getting Started guide.
  2. Open only one workflow guide at a time.
  3. Complete all steps in order.
  4. Run the verification checklist in each guide before moving on.

Guide format used in this category

Each guide follows the same structure:

  • When to use this guide
  • Required access
  • Step-by-step actions
  • Verification checklist
  • What happens after completion
  • Troubleshooting and escalation

How to get the fastest result

If you are new, use this exact sequence:

  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
  5. How to bulk download and install products
  6. Troubleshooting failed installs or updates

When to contact support

Contact support after completing a guide checklist and one retry attempt.

Include:

  • Account email
  • Site URL
  • Product name
  • Approximate timestamp
  • Expected result vs actual result

Related guides

  • Getting started with GrootMade
  • Troubleshooting failed installs or updates

Exact route paths

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

Expected UI state after each step

  • Step 1: Dashboard menu is visible with access to Licenses, Sites, and Billing.
  • Step 2: Documentation checklist can be followed without missing prerequisite screens.
  • Step 3: Customer can open each linked workflow page without access errors.
  • Step 4: Support route is reachable for escalation.

Screenshot map (step-level)

  1. Dashboard overview reference

  2. Operational flow visual

Operational objective

Complete the “About the Documentation category” 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/bookmarks
  • /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 overview reference
  • Step 2: Operational flow visual
  • 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 minutes
  • Owner: Customer Success
  • Last reviewed: 2026-03-18