How to install GrootMade Connect

Documentation
, , , ,
1

How to install GrootMade Connect

This guide covers the full install and connection procedure for GrootMade Connect, including pre-checks, validation, and rollback steps.

Required access: License with Site Manager support and WP admin access.

When to install GrootMade Connect

Install it when you want dashboard-managed installs and updates on a connected website.

Pre-install checks

Run these checks before installing:

  1. Confirm your license includes Site Manager.
  2. Confirm you can install plugins in WP admin.
  3. Confirm outbound requests from the site are not blocked by firewall rules.
  4. Confirm the site URL in WP matches the environment you intend to connect.
  5. Disable conflicting maintenance mode plugins temporarily if needed.

How to install

  1. Go to Sites in your GrootMade dashboard.
  2. Start the connect flow for your website.
  3. Follow the prompt to install GrootMade Connect.
  4. Activate the plugin in WP.
  5. Return to dashboard and complete connection confirmation.
  6. Open site details and verify the site reports as connected.

Verification checklist

Confirm each item:

  • Connected site appears under Sites
  • Connection status is healthy
  • You can select this site during install workflows
  • No repeated authorization prompts appear
  • Site metadata (URL/name) is correct

What happens after installation

  • The site appears in your managed sites list.
  • Install/update actions become available from dashboard workflows.
  • License-based feature gates are enforced automatically.

Rollback and troubleshooting

If connection fails repeatedly:

  1. Disconnect the site entry from dashboard.
  2. Deactivate and reactivate GrootMade Connect.
  3. Repeat the connect flow from the same account.
  4. If still failing, contact support with site URL and failure timestamp.

Related guides

  • How to manage connected websites
  • How to install plugins and themes from GrootMade Connect

Exact route paths

  • /dashboard/sites
  • /dashboard

Expected UI state after each step

  • Step 1: Sites page loads and connect action is visible.
  • Step 2: Connection flow starts for the chosen website.
  • Step 3: Connected status becomes healthy after plugin activation.
  • Step 4: Site can be selected in install workflows.

Screenshot map (step-level)

  1. Sites page connect workflow

  2. Connected dashboard confirmation

Operational objective

Complete the “How to install GrootMade Connect” 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/sites
  • /dashboard

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: Sites page connect workflow
  • Step 2: Connected dashboard confirmation
  • 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?

Support Engineering owns this guide and its periodic review cycle.

Guide metadata

  • Difficulty: Beginner
  • Estimated completion time: 15-30 minutes
  • Owner: Support Engineering
  • Last reviewed: 2026-03-18
1 Like