Plugin visibility issues usually come from workspace selection, installation status, required records, page publishing, access rules, or filters. Work through each layer before recreating anything.

What this guide helps you do

• Check whether the plugin is installed and active.
• Confirm records and pages are published or visible.
• Find access, filter, or workspace issues.

Before you start

• Know what is missing: plugin app, page, record, button, form, checkout, or customer activity.
• Confirm the expected workspace.
• Have the public page URL or plugin record name if available.

Do it manually

1. Confirm you are in the correct workspace.
2. Open Plugins and verify the plugin is installed and active.
3. Open plugin settings and check required setup warnings.
4. Review the record that should appear publicly.
5. Open the related page and check published or draft status.
6. Test the public URL in a fresh browser session if access rules are involved.

Ask Faster AI

• Troubleshoot why this plugin page is not visible. Check workspace, plugin status, required records, page status, and access settings.
• Review this plugin setup and list what could hide it from customers.
• Create a step-by-step visibility checklist for this plugin before I contact support.

Review before saving or publishing

• Do not duplicate plugin records until you know why the first one is hidden.
• Check access rules for members-only, paid, or private content.
• If visibility depends on dates or inventory, confirm availability is current.

Common issues and fixes

• If the plugin is missing, confirm installation in this workspace.
• If a record is missing publicly, complete required fields and publish or activate it.
• If only some customers cannot see it, review access, membership, payment, or invite rules.

Use it in daily operations

• Keep launch checklists for plugin visibility before campaigns go live.
• Document which pages and navigation links depend on each plugin.
• After troubleshooting, run a real customer-style test before announcing the fix.

Team handoff

• Write down what changed, who owns the next review, and which page, customer record, campaign, or plugin record should be checked next.
• If the work affects customers, include the public URL, test result, and any unresolved placeholder media in the handoff note.
• When Faster AI helped prepare the change, ask it to summarize the draft and review checklist so a teammate can approve the work without retracing every click.

Placeholder media

• Screenshot placeholder: add an annotated screenshot of troubleshoot plugin visibility with private customer, payment, and workspace details blurred.
• Video placeholder: add a short walkthrough that shows the manual path, the Faster AI prompt, and the review step before anything goes live.

Related help

• Choose the right plugin for a workflow
• Configure plugin settings
• Review plugin data in customer records