Getting started with GrootMade

Documentation
, , ,
1

Getting started with GrootMade

This guide gives you the full onboarding path from account setup to a verified first install, including checks for licenses, site connection, and feature access.

Required access: Any customer account with at least one active license.

When to use this guide

Use this guide if you are a first-time customer or if you want to reset and standardize your setup process across projects.

Prerequisites

Before starting, confirm all prerequisites:

  1. You can sign in to your GrootMade dashboard.
  2. At least one license is active.
  3. You have WP admin access for the target site.
  4. You can reach the site over HTTPS.
  5. You know whether this is staging or production.

How to get started

  1. Open dashboard and go to Licenses.
  2. Open your active license and record key limits (activations, bulk features, sublicense support).
  3. Go to Sites and start the connect flow for one site.
  4. Install and activate GrootMade Connect on the target site.
  5. Return to dashboard and confirm the site status is connected.
  6. Open one product and run a single install.
  7. Confirm install success in both dashboard and WP plugins/themes list.

Verification checklist

Confirm each item:

  • Site appears in Site Manager with healthy status
  • One product install succeeded end to end
  • License usage counters changed as expected
  • Feature badges match your subscription plan
  • You can reopen site and product details without errors

What happens after completion

After onboarding is complete:

  • You can use repeatable install/update workflows.
  • You can enable bulk workflows if your plan includes them.
  • Team handoff becomes easier because setup is documented and validated.

Troubleshooting

If setup fails:

  1. Recheck license state and available activation capacity.
  2. Reconnect the site from the same account.
  3. Retry one single-product install.
  4. Escalate with timestamp, site URL, and product name if still failing.

Related guides

  • How to install GrootMade Connect
  • How to activate your license
  • How to bulk download and install products

Exact route paths

  • /dashboard
  • /dashboard/licenses
  • /dashboard/sites

Expected UI state after each step

  • Step 1: Active license card is visible under Licenses.
  • Step 2: Feature badges and limits are visible for the selected plan.
  • Step 3: New site appears in Sites after connection.
  • Step 4: Product install action is available for connected site.
  • Step 5: Install completion state appears in dashboard and WP.

Screenshot map (step-level)

  1. Dashboard onboarding entry point

  2. Site management reference

Operational objective

Complete the “Getting started with GrootMade” 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

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 onboarding entry point
  • Step 2: Site management reference
  • 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: 15-25 minutes
  • Owner: Customer Success
  • Last reviewed: 2026-03-18