CPD Support
Feature Overview
The CPD Support Center (/cpd/support) is the in-app help surface for CPD users: a tabbed page with the User Guide, instructional videos, public and member policies, an FAQ forum, and the Program-Level-Requirement tools & forms, plus a contact-support email affordance. Split out of cpd.md on 2026-05-27 so each CPD area has its own spec/page. ACs below describe the built behaviour and are citation-linked to the code (the railway track: spec ↔ code ↔ BDD).
Open Questions
All questions have been answered.
Acceptance Criteria
- ✅
cpd.support.center-tabs— the CPD Support Center at/cpd/supportrenders a tabbed help page with: User Guide, Instructional Videos, Public Policies, Member Policies, FAQ Forum, and Program Level Requirements Tools and Forms. ‡ - ✅
cpd.support.contact-email— the page exposes a contact-support email affordance resolved from the configured support address. ‡ - ✅
cpd.support.plr-tools-forms— the "Program Level Requirements Tools and Forms" tab surfaces the PLR clinical forms (Culturally Safe Practice / Addressing Health Inequities / Professionalism / Ethics tools; wording corrected by #12150, 2026-09-01), aligned with the forms seeded incpd-resource-library.md(cpd.resource-library.forms-seed). ‡ - ✅
cpd.support.plr-labels-canonical— the CPD Support guidance pages render the four PLR labels in canonical wording, governed bycpd-home.md(cpd.home.plr.canonical-label-consistency); no older wording ("Cultural Safety", "Maintaining Professionalism", bare "Health Inequities", "Ethical Practice") remains. † † ‡ - ✅
cpd.support.faq-moderation-queue— the FAQ Forum's pending queue is drainable: a Super Admin reaches it at/admin/faq-moderation(guarded byAdminRoute, listed in the super-admin sidebar cluster) and can approve, reject or edit a member's pending question or answer. Approving is what makes the member-facing "it will appear here once approved" copy true —listApprovedfilters onstatus='approved', so before this route existed nothing could set that status and the queue accumulated indefinitely. Server-side authorisation isadminProcedure, not the client guard. (#11053) ‡ - ✅
cpd.support.faq-moderation-queue.bounded— the queue survives its own inputs: member submission (faqQuestion.submit,faqAnswer.submit) is rate-limited, and the pending list is paginated oldest-first with a capped page size, so no member can flood pending rows and degrade the only screen able to drain them. A capped page states that more items are waiting rather than presenting itself as the whole queue. (#11053) ‡ - ✅
cpd.support.faq-moderation-queue.attributable— every moderation action is attributable before it takes effect:editFaqItemresolves the moderator and refuses the write if it cannot, and thefaq_editaudit row records a keyed HMAC-SHA256 digest of the pre-edit content (never the content itself) plus both lengths, so an edit to a member-attributed post that is then published can be evidenced without copying member free text intoaudit_trail. The digest is keyed rather than a plain hash (#11088): a moderator edit is typically a REDACTION and the redacted span is short and guessable, so an unkeyed digest would be an offline confirmation oracle for exactly the identifiers the hashing exists to avoid storing. It is computed BEFORE the content write, so a missing secret aborts the edit rather than leaving content mutated with no audit row. (#11053, #11088) ‡ - ✅
cpd.support.remediation-tile— the Support Center's tile grid includes a Request Remediation Support tile, opening the remediation self-referral form. It sits with the other two request-action tiles (Exemption, Review or Appeal) and keeps Contact Support last. The tile is the Member Dashboard intake channel the published remediation policy names; the behaviour behind it — intake schema, referral sources, and the practitioner/CPD-Advisor/Super-Admin visibility rule — is owned bycpd-remediation.md(cpd-remediation.intake.dashboard-form), not this spec. (#11673) ‡ - ✅
cpd.support.appeal-fee-figure— the appeal affordances in the Support Center (the appeal form and the User Guide's appeals content) quote the appeal fee from the sharedREVIEW_APPEAL_FEESconstant — $600 AUD (ex GST) per the published Review and Appeal Policy July 2026 — never a hard-coded literal, and the stale pre-July-2026 "$165 (incl. GST)" figure appears nowhere. The constant itself is owned bypayment.md; a future fee change is made once inpackages-shared/ppp/src/constants/pricing.tsand flows to every surface. (#11034) ‡ - ✅
cpd.support.member-notification— submitting the exemption or appeal form gives the member an acknowledgement carrying a reference number: the mutation's returned submission id is surfaced in the success snackbar ("Reference number:{id}"), a matching acknowledgement email is sent to the submitter, and the submission is written to the audit log. Fulfils the July 2026 policies' promise (Review and Appeal § Part A.2/B.2, Granting Exemptions § 4) that was previously unmet — the{id}returned by the submission mutation was discarded and the only email sent was the internalexemptions@/appeals@staff notification. The companion outcome-notification email/audit path (notifyComplianceFormDecision) exists as the integration point for a decision-recording caller but is not yet wired up — decision persistence and authorization are tracked separately. In-app timeframe-copy drift and mailbox-address consistency across these surfaces (AC4/AC5 of the source issue) are not addressed by this AC. † ‡ (#11049) - ✅
cpd.support.review-path— the Support Center offers a Request a Review tile, distinct from the appeal tile, mounting a form on which the member chooses an internal review (same assessor, no fee) or a formal review (different assessor, at a fee) perReview and Appeal Policy July 2026§ Part A.2. The quoted cost follows the selected tier from the sharedREVIEW_APPEAL_FEESconstant rather than being restated per surface — same single-source pattern ascpd.support.appeal-fee-figure. Before this, no'review'formType existed anywhere in the system and one "Request Review or Appeal" tile opened the appeal form unconditionally, so a member seeking the free internal review the policy offers was shown a form whose own copy said a fee applies. The request also carries the member's registration number and preferred contact method, both of which § Part A.2 makes mandatory. (#11050) † ‡ - ✅
cpd.support.appeal-gated— the appeal form is gated on a completed formal review, per § Part B's "An appeal can only occur following completion of a formal review". A member with no completed formal review sees an explanation and a pointer to the review path instead of the form, and the appeal itself names which completed review it follows. The gate is enforced server-side as well —submitAppealverifies the named review exists, belongs to the caller, is a formal review, and has been decided, throwingPRECONDITION_FAILEDotherwise — because hiding a form does not make its mutation unreachable. A pending formal review does not unlock the path; only a decided one does. (#11050) † ‡ - ✅
cpd.support.exemption-documentation— the exemption form requires at least one file attachment, perGranting Exemptions Policy July 2026§ 1's "Both application options require submission of… supporting documentation, such as medical certificates". Files upload through the existing user-scoped storage router and only their storage keys reach the submission mutation. Enforced at both layers: the submit control stays disabled while no document is attached, andattachmentKeyscarries a.min(1)server-side so the mutation is not reachable around the disabled button. Previously the form had four text controls and no upload affordance at all, so a member had to email their medical certificate separately from the request it supported. (#11050) † ‡ - ✅
cpd.support.exemption-duration-bounds— an exemption period is bounded to 6–12 months per § 2, enforced in the tRPC input schema (not only in the form) and surfaced inline as the member picks dates. The bound is compared at day resolution, not by flooring to whole months: a period one day past the 12-month date still floors to 12 and would otherwise pass. § 1's "Exemptions will not normally be granted for consecutive CPD Years" is also now detectable — an approved prior exemption overlapping the preceding CPD year is surfaced as a warning, not a block, because the policy says "not normally" and the decision remains the assessor's. Before this, validation checked date format and ordering only: a 1-day or a 5-year exemption submitted successfully, and no prior submission was ever read. (#11050) † ‡ - ✅
cpd.support.exemption-grounds— the exemption form carries a required grounds selector mapping to the policy's categories (medical, parental/carer leave, bereavement, cultural responsibilities, other). This is the platform-side precondition for § 3's absolute guarantee that "No exemption/variation requests related to cultural responsibilities will be assessed without input from PPP's Cultural Advisor": a cultural-grounds request is now detectable, is routed to the Cultural Advisor mailbox instead of the ordinary exemptions inbox, is marked as a referral in its audit-trail metadata, and tells the member the referral will happen. Previously the form captured no grounds category at all and routing was a static two-entry mailbox map with no branch, so nothing in the system could tell a cultural request from any other. The human referral process itself remains outside the platform; this AC covers only the precondition that made it unrepresentable. (#11050) † ‡ - ✅
cpd.support.subscription-fee-figure— the User Guide's "Fees and Inclusions" section (Initial Registration fee, Annual Fee) renders the CPD Home subscription price via<PriceLabel plan="cpd" currency="AUD" hideBillingPeriod />(components/pricing/PriceLabel.tsx), which readsPLAN_PRICES.cpdfrompricing.ts, rather than the literal"$299 AUD (incl. GST)"string it previously hard-coded. Same single-source pattern ascpd.support.appeal-fee-figureabove, extended fromREVIEW_APPEAL_FEEStoPLAN_PRICES— a future price change is made once inpricing.tsand flows to this surface automatically. (#11801, Phase 2 of #8069) † ‡
Open GitHub Issues
Open issues on label:feature:cpd-support — no open issues. Fetched at: 2026-10-13T07:29:49Z — live list on GitHub.
Change Log
| Date | Change | PR/Issue | Reason |
|---|---|---|---|
| 2026-08-31 | Split the Support Center's review/appeal tile into a Request a Review path (internal, no fee; formal, at a fee) and a Lodge an Appeal path gated on a completed formal review; the exemption form now requires at least one supporting document (enforced at both the submit control and the server-side schema), a required grounds category, and a 6-12 month period bound with a consecutive-CPD-year warning. New ACs cpd.support.review-path, cpd.support.appeal-gated, cpd.support.exemption-documentation, cpd.support.exemption-duration-bounds, cpd.support.exemption-grounds. | #12120, #11050 | Review and Appeal § Part A.2 offers a free internal review and § Part B allows an appeal only after a completed formal review, but no review formType existed and one tile opened the appeal form unconditionally; Granting Exemptions § 1/2/3 require supporting documentation, a 6-12 month period and a Cultural Advisor referral for cultural grounds, none of which the form could capture or the validators enforce (#11050). |
| 2026-08-23 | Exemption/appeal submission now shows the member a reference number, emails them an acknowledgement, and writes an audit log entry; new AC cpd.support.member-notification. | #11745, #11049 | The July 2026 policies promise the submitter acknowledgement, a reference number and an outcome notification, but the platform only emailed the internal compliance mailbox and discarded the returned submission id (#11049). |
| 2026-08-01 | Appeal form and User Guide now quote the $600 AUD (ex GST) appeal fee from the shared REVIEW_APPEAL_FEES constant; new AC cpd.support.appeal-fee-figure. | #11255, #11034 | In-app fee ($165 incl GST) had drifted from the published Review and Appeal Policy July 2026 ($600 ex GST) — the figure doctors saw was not the figure the policy charges (#11034). |
| 2026-07-27 | faq_edit audit digest is now a keyed HMAC computed before the content write, and the spec's code-paths now claim the supportServices directory it describes. | #11092, #11088 | An unkeyed digest of a short, guessable redaction is an offline confirmation oracle for the identifiers it exists to avoid storing. Keying it introduced a secret lookup that can throw, so it moved ahead of the write to avoid mutating content with no audit row. |
| 2026-07-27 | Added AC cpd.support.faq-moderation-queue — the FAQ Forum's pending queue is drainable by a Super Admin at /admin/faq-moderation (approve, reject, edit) — plus .bounded (rate-limited submits, paginated capped queue) and .attributable (moderator resolved before the write; faq_edit audits a SHA-256 digest of the pre-edit content, never the content). Corrected the four stale pre-reorganisation modules/Support path citations to modules/admin-org/support, and updated the code-paths and bdd-features front-matter to match. | #11079, #11053 | ModeratorInterface existed and worked but was never mounted, so nothing could move a question out of 'pending' while listApproved filters on status='approved' — the queue accumulated indefinitely (#11053). The path citations had gone stale in the modules/Support to modules/admin-org/support move, which is likely how the missing mount escaped notice. Mounting the screen made three pre-existing service-layer weaknesses reachable for the first time, fixed in the same PR after security review — unbounded member submits feeding an unbounded queue read, an edit that mutated content before resolving the moderator, and a faq_edit audit row that recorded only contentLength. |