{
  "slug": "bw-lead-ai",
  "name": "BW Lead Attribution Intelligence",
  "version": "1.10.0",
  "download_url": "https://plugins.bowden.works/wp-content/uploads/plugin-updates/bw-lead-ai-1.10.0.zip",
  "download_hash": "sha256:833a88a4637766de55e8d5c348176a39f5be82215bfa101b0b89311dc3601b5f",
  "download_size": 533258,
  "requires": "6.0",
  "tested": "",
  "requires_php": "7.4",
  "last_updated": "2026-08-13",
  "homepage": "https://plugins.bowden.works/bw-lead-ai/",
  "author": "Bowden Works",
  "description": "Capture traffic source, attribute it to every lead, and understand where your leads are coming from.",
  "changelog": "## [1.10.0] - 2026-08-13\n\n### Added\n- **Two capabilities, so reading enquiries no longer requires running the site.**\n  Everything here used to need `manage_options` — which is not \"can see lead\n  reports\", it is every Settings screen on the site and the capability most\n  plugins treat as \"is this an administrator\". Somebody whose job is to read\n  enquiries had to be handed the keys to everything to do it.\n\n  - **`bw_lead_ai_view`** — journeys, reports, the attribution screens, Help.\n  - **`bw_lead_ai_manage`** — settings, cross-domain configuration, retention,\n    the setup wizard, imports, exports, resets, reprocessing and purging.\n\n  The split is the point. Somebody reading enquiries should not be one wrong\n  click from switching on data handoff, widening what is collected or shortening\n  how long it is kept — those have privacy consequences and none of them is a\n  decision that belongs to the person reading the reports.\n\n  **Nobody loses a screen.** Anyone who can `manage_options` holds both\n  capabilities automatically, so every existing site — including any role\n  somebody built with `manage_options` — keeps working with nothing to do. Both\n  are also added to the administrator role so they appear in whatever tool you\n  use to assign capabilities.\n\n  The read capability is what the top-level menu is gated on, so it is visible to\n  the people it is for; the settings entries inside it are gated separately.\n  Opening Settings as a read-only user now lands on Reports rather than a blank\n  screen.\n\n  Both names are filterable — `bw_lead_ai_view_capability` and\n  `bw_lead_ai_manage_capability`. The older `bw_lead_ai_view_journey_capability`\n  still works and now narrows journeys alone.\n\n### Fixed\n- **A read-only user could be offered a menu item that led to a blank page.**\n  When WordPress refuses a submenu entry it adds a link back to the parent\n  carrying the parent's capability — and the parent's screen is Settings, which\n  renders nothing for somebody who cannot configure. Found by testing the menu as\n  a read-only user rather than by reading the code."
}