Platform Updates

Partners Dashboard V2 now has a native protected account-setup surface using the existing Worker contracts: profile and Philippine address details, optional reviewed RegoSite import, four full scroll-gated legal acknowledgements, a drawn signature, optional passkey enrolment, and policy-controlled TOTP enrolment. Anonymous visitors return through native sign-in with the intended setup destination preserved. No Partners API behavior changed.

Authenticated profile saving and MFA/passkey enrolment still need real-session browser certification before this surface is ready for a production rollout.

The approved Terms, Privacy Policy, NDA, and Policies are also available through shared V2 public legal pages and document embeds. The generated third-party-notices inventory is still being ported separately.

The V2 third-party notices page now carries the 17-row legacy inventory with source links and an accessible license dialog. Package-specific notice addenda still require verbatim carryover before legal-content certification.

Partners Dashboard V2 now has a native, protected guide hub with the existing six operational guide topics and quick-reference severity, report-status, and ban-type material. It reuses the shared dashboard shell and guide-card pattern; no Partners API behavior changed. The detailed guide articles are still being ported and are not yet production-certified.

The complete Getting Started article is now available through the same reusable guide article surface, including partner scope roles, platform-section explanations, and linked first steps.

The CMS article is now also native in V2, including scoped CMS launch guidance, the secure handoff boundary, troubleshooting, and a link to the CMS’s own guide.

The complete Reports guide is now native in V2 as well, covering lifecycle, severity, filing, enforcement, watchlists, profiles, audit history, and network sharing.

The V2 Event Setup guide is also now native, covering the event-launch order, registration and payment configuration, conditions of entry, optional operations modules, and a safe-launch checklist. Production-build revalidation is pending host disk capacity.

Partners Dashboard V2 now has a native settings entry point for Profile, Account Security, Organization, and Platform Status. It uses the shared dashboard shell and reusable route-card surface; the individual settings workflows continue to be ported separately. No Partners API behavior changed.

Partners Dashboard V2 now renders the protected Reports overview from the existing scoped Worker read contracts: totals, personal reports, recent bans, revisions, and incidents. Report and ban links stay inside the native V2 routes, while filing, editing, enforcement changes, and appeal workflows remain intentionally separate until their controlled forms are ported. Local type-check, production build, source-drift verification, whitespace validation, and authenticated browser read verification passed; no Partners API behavior changed.

The native report-filing flow is now also available. It uses the same Worker-owned incident payload as the existing dashboard, keeps the safety report’s person, victim, witness, evidence, action, declaration-signature, and cross-community recommendation fields visible, validates required information, and presents a final confirmation before any report is transmitted. No certification submission was created, and report editing, cross-ban, and appeal workflows remain separate ports.

Repositories: partners.furries.ph

What’s Changed

• Creating or editing a standalone campaign in Affiliates & Tracking now writes the campaign immediately and reloads the server-confirmed value.
• A failed write remains in the editor with a clear error instead of appearing saved only until the page reloads.

What To Do

• Event operators can use Create campaign or Save changes in the campaign dialog; the dashboard confirms the saved campaign before closing it.

Partners Dashboard V2 now supports the existing conversion reward configuration in Affiliates & Tracking. Event operators can set milestone thresholds, optional reward descriptions, sales-to-point conversion, and tier/add-on point rules from the event’s existing catalog. The dashboard validates the same conversion requirements before staging the server-owned finance-program update. Commission payout account details remain protected and are not exposed in the dashboard. No Partners API behavior changed.

Partners Dashboard V2 now includes event HR department policy and membership composition. Operators can maintain locations, departments, department-level subsidy and volunteer-window overrides, and member roles from the existing Worker contract. The member picker reuses the existing event-account search, prevents duplicate department assignments, and the prior-event import carries the full HR structure into a fresh event-local draft. No Partners API behavior changed.

Partners Dashboard V2 now supports ordering reusable Conditions of Entry documents, assigning them to activity forms, and reviewing a local document preview alongside the existing shared-flow assignments. All changes remain a single event-owned conditions snapshot, so registration and related attendee workflows keep one consistent set of required documents. No Partners API behavior changed.

Partners Dashboard V2 now includes reusable payment-account editing and provider fee configuration. Event operators can maintain account identifiers, limits, balances, instructions, active and preferred status, plus fixed or percentage provider fees in the existing event-owned payment configuration. QR image upload remains separate because it uses the managed-asset boundary. No Partners API behavior changed.

Partners Dashboard V2 now provides item, movement-type, and date filters for event inventory history, plus CSV export of the filtered result. Stock counts and point-of-sale settings remain part of the same existing event-owned inventory contracts. No Partners API behavior changed.