Integration hub for delivery systems
WebRiskOps sits between scanner evidence, report findings, remediation workflow and the external systems where teams plan, assign, fix and review work.
- Ticket export: Jira, GitHub Issues, GitLab Issues, Bitbucket, Trello, Linear, Azure DevOps, YouTrack and Asana
- Repository and platform handoffs: GitHub, GitLab, WordPress/WooCommerce, Shopify and GTM/CMP context
- Every connection stays scoped, revocable, audited and tied to evidence instead of becoming a blanket production-access grant
Extension add-on boundary
Extensions are account-level add-ons that support evidence capture and diagnostic handoff. They do not grant entitlement before provider confirmation, bypass project authorization, or change production systems automatically.
- Account-level add-on state
- Provider webhook confirmation before access
- No authorization or scope bypass
Browser evidence capture access
Browser capture is started by the customer on the active page and sends bounded evidence to a selected project or report context.
- User-initiated active tab capture only
- Page URL, title, selected text, headings and report context
- No cookies, storage, password fields, payment fields, full HTML or browsing history
WordPress/WooCommerce diagnostics access
The WordPress/WooCommerce add-on uses an authenticated admin handoff for diagnostic metadata such as platform versions, active theme/plugin names and checkout page context.
- Customer-approved WordPress admin action required
- No customer, order, payment, database dump or credential collection
- No uncontrolled post, option, theme, plugin or file changes
Shopify diagnostics access
The Shopify diagnostic add-on uses managed app installation and read-only scopes that support storefront and theme diagnostics without commerce write access.
- Read-only Shopify scopes: read_content, read_products and read_themes
- No orders, customers, payment methods, gift cards or write scopes
- Compliance webhooks remain separate from ordinary diagnostic handoff
Agency distribution access
Agency distribution is limited to agency billing accounts and client-scoped controls so extension evidence cannot cross client workspaces.
- Agency billing account required
- Assigned client projects only
- No cross-client evidence sharing or unrestricted client access
Mobile app planning boundary
Mobile app support is planning-only until native package ingestion, runtime scanner execution and platform-specific review boundaries are explicitly enabled.
- No APK, AAB, IPA or runtime mobile scanner ingestion yet
- No store approval, privacy-law, accessibility conformance or certification promise
- No production user data extraction or binary modification
Activation and support path
Use billing to review plan or add-on availability, provider mapping state and checkout blockers. Use support only when the product workflow cannot explain the next safe step.
- Review plan status in billing
- Keep provider IDs and secrets out of support text
- Use support with account, plan and project/report context
