How to install plugins and themes from GrootMade Connect

Documentation
, , , ,
1

How to install plugins and themes from GrootMade Connect

This guide provides a full single-product install and update runbook, including staging-first workflow and post-install validation.

Required access: Connected site plus license access for the selected product.

When to use this workflow

Use this when you want a controlled install or update for one specific plugin or theme.

Pre-install checks

Before each install/update:

  1. Confirm the product is included in your plan.
  2. Confirm target site is connected and healthy.
  3. Confirm you selected the correct environment (staging or production).
  4. Optional: snapshot/backup site state for safer rollback.

How to install or update

  1. Open a product in your dashboard.
  2. Choose the connected target site.
  3. Start the install or update action.
  4. Monitor operation status until completion.
  5. Confirm completion in dashboard and WP admin.
  6. If this is production, run quick smoke checks on key pages.

Verification checklist

After install/update, verify:

  • Expected version is visible
  • Plugin/theme is active
  • Main pages load without fatal errors
  • No blocked dependency warnings
  • License status remains valid

What happens after install

  • Product version status updates in your management workflow.
  • Access controls continue to follow your current plan.
  • The same flow can be repeated for staged rollouts.

Troubleshooting

If a product is locked, verify your plan includes the product tier and that your license is active.

Related guides

  • How to bulk download and install products
  • Troubleshooting failed installs or updates

Exact route paths

  • /dashboard/sites
  • /dashboard/history
  • /dashboard

Expected UI state after each step

  • Step 1: Product install/update action is available.
  • Step 2: Target site selector lists only connected sites.
  • Step 3: Operation status transitions to completed.
  • Step 4: Installed version is visible in WP and dashboard history.

Screenshot map (step-level)

  1. Install action from dashboard

  2. Connected sites for deployment

Operational objective

Complete the “How to install plugins and themes from 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/history
  • /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: Install action from dashboard
  • Step 2: Connected sites for deployment
  • 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: Intermediate
  • Estimated completion time: 15-25 minutes
  • Owner: Support Engineering
  • Last reviewed: 2026-03-18