Your account
HOL-D099Story implementation: Planned

Apply to become a Commercial Partner

commercial · Proposed launch phase 4

Start from Home

Review as Organization owner · Full workflow planned

User story

As a organization owner, I want to apply to upgrade our organization to Commercial Partner so we can request the agreed commercial features.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • FOLLOW-UP ONLY: keep the free organization and its owner/manager assignments intact while preparing a Commercial Partner application.
  • Managers may prepare business information and draft the application. Only the current verified owner may submit and accept the associated versioned terms.
  • Track draft, submitted, information requested, approved or declined with reasons and next actions; HOL Commercial manager owns the review under D100.
  • Commercial Partner is organization status, not a separate login, personal membership upgrade or HOL staff role. Pending applications grant no enhanced feature access.
  • Keep individual sponsorship/campaign/content approvals separate. Pricing, payment, specific enhanced features, activation/expiry/revocation rules and vetting evidence remain unselected; do not implement or invent them.

What to check in the demo

Follow these steps from the role’s landing page through navigation and feature checks.

Review asStart here: Home

Begin in a named organization workspace as its current owner. The local Organization owner choice uses Maya Hart → Teton Meadow Guides; current assignments may change during reviews. Choose the organization in the account/workspace menu. Personal account security remains separate.

Navigation from sign-in

  1. 01Open the fictional Organization owner account through the connected sign-in service. Seeded Home review opens directly. Real HOL staff access and protected actions require an authenticator check.
  2. 02Follow-up review begins from an owner’s named organization Home, then Commercial Partner application. The application screen is not built in this increment.

Feature checks start here

Apply to become a Commercial Partner · Full workflow planned

Follow-up Planned; implementation is on hold. No application, live payment or partner activation is built.

  1. 03Current UI review: follow the navigation as far as the explicitly available screen; the complete feature below is not built. Stop when the named control is absent.
  2. 04Planned acceptance — When authorized later, review manager draft preparation, owner-only submission/terms and information-requested/approved/declined outcomes.
  3. 05Planned acceptance — Confirm pending status does not unlock partner features and organization approval does not approve individual sponsored material.

Backend work for this feature

Requirements only · Backend implementation on hold

What needs to be supported

  • When later authorized, model a versioned organization application, manager-prepared draft, owner submission, accepted terms version/time, private evidence and decision state; pricing/payment/activation are undefined and must not be fabricated.
  • Use one trusted account ID; keep email verification, professional labels, reader entitlement, organization-scoped access and internal HOL staff assignments independent.
  • Validate actor, organization/person IDs, current access and expected revision at the trusted boundary. Remembered workspace, URL, fixture choice and client flags never grant permissions.
  • Persist only the records needed for this outcome, including owner-scoped drafts and decision/assignment/consent audit where applicable. Keep private evidence and contacts out of public projections.
  • Enforce the selected requirements above in database/API policies, with idempotent transitions, concurrent-update handling and denied cross-account writes.
  • Keep this workflow unimplemented until the follow-up receives authorization and its vetting/activation rules are defined.

How to verify when implementation is approved

  1. Follow-up design must distinguish manager preparation from owner-only submission and terms, and keep pending applications from granting partner rights.
  2. Test owner, manager, unrelated account, unverified account and permitted HOL staff where relevant; deny self-grants and cross-organization access.
  3. Exercise success, interrupted/repeated requests, expiry/revocation and stale/concurrent updates; verify stable identity, correct public visibility and preserved unrelated account data.

Before this can work

  • Begin in a named organization workspace as its current owner. The local Organization owner choice uses Maya Hart → Teton Meadow Guides; current assignments may change during reviews. Choose the organization in the account/workspace menu. Personal account security remains separate.
  • Use a fictional organization owner account and begin at its Home with its actual permitted context.
  • Keep simulated outcomes separate from real account/backend evidence.

Connected stories