BlackOakAdmin

Admin sitemap guide

32 admin screens · 18 built · 14 planned or stubbed

Workflows

Start here. Each chain is one governance journey, in order — click a step to see what it does, who feeds it, and who uses the result (including in the consumer and merchant apps).
Govern who can do what
Control administrative access and keep privileged actions accountable.
Onboard and govern a merchant
Decide who may sell on the Marketplace, and keep them compliant.
Approve what may be sold
Review products and services against category policy before they reach shoppers.
Withdraw a product
Take a product off sale and deal with orders that already contain it.
Resolve an escalation
Decide disputes a shopper and merchant could not settle between them.
Commercial terms & reporting
Set what the Marketplace charges and check the money reconciles.
Operations oversight
Case management queuePlaceholder/oversight/casesHow it works →
Case decisionPlaceholder/oversight/cases/:caseIdHow it works →
Configuration & rules
Feature-flags managementPlaceholder/config/feature-flagsHow it works →
Reference-data managementPlaceholder/config/reference-dataHow it works →

Outside the apps

Participants in these workflows that are not screens in any of the three apps. Each explains where the ownership boundary sits.
Marketplace servicesOutside the apps
The Marketplace back-end: catalog, inventory, orders, returns, cases, reviews, the rules engine, RBAC, and the configuration registry.
BlackOak CommerceOutside the apps
The financial platform: funding, per-merchant allocation, refunds, and the rewards ledger.
Sends SMS and email on behalf of every BlackOak product.
Shipping carrierOutside the apps
Labels and tracking scans that move an order to the doorstep, and carry returns back.
Where an escalated delivery-issue case is worked and tracked by BlackOak support.
Sets the policy the Marketplace enforces: approved categories, restrictions, disclosures, and the PHI position.
Built screens link to their shipped route; planned and API-ready screens link to their placeholder. Merchant directory / search reuses the existing /merchants surface until its own screen ships.