Plugin settings control how the plugin behaves for customers and your team. Review settings before launch and again after the first real interactions.

What this guide helps you do

• Find required plugin settings.
• Configure public behavior, data, payments, access, and notifications.
• Know what to test after changing settings.

Before you start

• Open the plugin in the correct workspace.
• Know the workflow owner and launch date.
• Gather required values such as prices, staff, policies, sender details, categories, or access rules.

Do it manually

1. Open Plugins and select the installed plugin.
2. Review required settings and any setup warnings.
3. Configure business details, records, availability, pricing, access, notifications, and page behavior as relevant.
4. Save changes and preview customer-facing pages.
5. Run one test interaction and inspect the resulting customer or Money record.

Ask Faster AI

• Review this plugin settings page and tell me what is missing before launch.
• Set up plugin settings for a small service business workflow. Ask before changing payment or public page settings.
• Create a test plan for this plugin, including Customer 360 and notification checks.

Review before saving or publishing

• Check settings that affect payments, customer access, notifications, or public page content.
• Preview desktop and mobile pages after changing design-related settings.
• Confirm internal notes are not visible in public descriptions or confirmations.

Common issues and fixes

• If settings will not save, check required fields and permissions.
• If customers see stale details, refresh the preview and confirm the correct record is published.
• If plugin data does not reach customers or Money, review the plugin connection and test again.

Use it in daily operations

• Revisit settings after pricing, availability, policy, or staffing changes.
• Document who owns routine updates for each plugin.
• Use AI to prepare review checklists, but approve customer-facing settings manually.

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 configure plugin settings 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
• Review plugin data in customer records