Best practices for marketplace template import
Last updated: 7 May 2026
What this does
Use this guide to evaluate, import, and adapt marketplace templates before using them with real teams or projects.
Current access and functionality
- Verified against the current
impact-web,impact-client, andimpact-marketplacecode on 2026-05-07. - Purchase and ownership are handled through marketplace flows and inventory/order history.
- Import actions usually happen from the destination feature in
impact-webor supported mobile flows. - Supported template destinations include checklists, projects/playbooks, risks, competencies, and questionnaires where enabled.
- Import requires ownership, matching template type, active workspace, and management permission for the destination.
Import review checklist
- Confirm the item type matches the destination feature.
- Review version, language, merchant, price, and preview content.
- Confirm the workspace or project that will receive the import.
- Import into a controlled area first when the template affects many users.
- Rename and adapt the template to match your team’s terms.
- Remove irrelevant tasks, questions, risks, or checklist items.
- Test the template with one small team before broad rollout.
Governance practices
- Keep one admin accountable for each imported template.
- Record why the template was imported and where it is used.
- Review imported templates quarterly.
- Retire templates that no longer match current operations.
Common issues
- Issue: The item is owned but not importable. Fix: Check destination type, workspace selection, and admin permission.
- Issue: Staff see a confusing imported checklist. Fix: Adapt wording and evidence requirements before assigning.
- Issue: Marketplace purchase does not appear. Fix: Confirm the same account is signed in and check order history or inventory.