Skip to main content

​
Search, Support, and Legal Reference

This guide covers platform-level utility workflows outside core campaign operations. Use global search to quickly navigate to:
  • pages/modules
  • campaigns
  • links
  • rules
  • related operational entities
Best practice:
  1. Start broad with entity name.
  2. Narrow by module context (campaign/link/rule).
  3. Confirm active workspace before taking actions.

​
Support and feedback workflows

Typical channels include:
  • in-app feedback form
  • bug-report pathway
  • feature-request pathway
  • support/help page workflows
Guidance:
  • include workspace context and timestamps in support requests.
  • include screenshots/filter context for analytics issues.
  • classify requests by bug/feature/onboarding to speed routing.

​
Notification and communication context

Supportability depends on notification setup. Validate:
  • key operational alerts are enabled for responsible users.
  • billing and payout notifications reach monitored inboxes.
  • incident responders receive relevant integration/webhook alerts.
Customer-facing legal surfaces typically include:
  • Terms of Service
  • Privacy Policy
Operational expectations:
  • keep policy links visible in appropriate product areas.
  • reference policy in partner/customer dispute workflows when relevant.
  • align onboarding and invite flows with current policy versions.

​
Enterprise contact and sales pathways

For enterprise-style requests, operators typically route users through dedicated contact flows and qualification forms. Where forms are used, anti-abuse controls (for example CAPTCHA) should be enabled and tested.

​
Troubleshooting

Related:
  • /user-guides/manual/workspace/settings-and-preferences
  • /user-guides/manual/workspace/security-and-compliance
  • /user-guides/manual/foundations/feature-map-by-page