Skip to main content

Creator Admin and Pro Feature Context

Source: .agents/references/features/creator-admin-and-pro.md

Content​

Creator Admin and Pro Feature Context

Purpose​

Creator admin and pro surfaces support community owners and internal/admin users managing products, plans, payouts/revenue, KYC, business setup, announcements, leads, ads/content checkout, pro subscriptions, and creator tooling. These flows often depend on authenticated community ownership and service contracts rather than public visitor state.

User-Facing Workflows​

  • Creators configure communities, products, announcements, plans, payouts, KYC, and business/profile settings.
  • Pro and plan overlays guide creators through subscription or upgrade flows.
  • Admin/pro pages may show revenue, abandoned checkout, affiliates, lead forms, co-founder chat, content generation, and creator setup prompts.
  • KYC surfaces show under-review/status badges and should not overstate verification state.
  • Creator workflows should avoid interrupting public member/visitor flows unless explicitly linked.

Key Entrypoints​

  • Features:
    • src/features/KycVerification/
    • src/features/ProCheckout/
    • src/features/ProOverlayWrapper/
    • src/features/ProSubscriptionOverlay/
    • src/features/ProSubscriptionSuccessScreen/
    • src/features/NasioProcessingFee/
    • src/features/AbandonedCheckout/
    • src/features/Affiliates/
    • src/features/Announcements/
    • src/features/LeadForms/
    • src/features/MagicAdsCheckout/
    • src/features/MagicContentCheckout/
    • src/features/CoFounderChat/
    • src/features/ConnectChatPlatform/
    • src/features/ConnectGoogleCalendar/
    • src/features/CustomizeEmailMessages/
    • src/features/BusinessSetupOverlay/
  • Routes:
    • src/pages/portal/
    • src/pages/choose-a-plan/
    • src/pages/subscribe-plan/
    • src/pages/integration/
    • src/pages/user/
  • Hooks:
    • src/hooks/useNasPlan.ts
    • src/hooks/useCommunityRevenue.js
    • src/hooks/useUserCommunities.ts
    • src/hooks/useUserRoleInCommunity.ts
    • src/hooks/useTierApplicationConfigCreate.js
  • Services:
    • src/services/nasPlan/nasPlanService.js
    • src/services/moneyPageService.js
    • src/services/leadFormsService/
    • src/services/magicLeadsService.ts
    • src/services/affiliatesService.ts
    • src/services/announcementService.js
    • src/services/faiqService.ts
    • src/services/coFounderService.ts
    • src/services/sessionAnalytics/sessionAnalyticsService.js

Data Flow and Service Boundaries​

  • Creator/admin surfaces frequently rely on authenticated service helpers. Preserve authorization checks and do not move owner-only logic into public components.
  • Plan/pro and checkout flows overlap. Load checkout-and-payments.md when touching subscription purchase, payment provider, or pricing behavior.
  • KYC status components should use existing constants and status mapping from src/features/KycVerification/.
  • Revenue and analytics screens should preserve query/date filters and avoid logging sensitive financial or user details.
  • Lead forms, announcements, integrations, and chat/calendar connectors can have external service contracts. Inspect service types before changing payload shape.
  • Magic Content creation supports deep links on /portal/magic-content: style=image|video selects the initial creation type and overrides legacy assetType, styleId preselects a MagicContentStyleAsset, externalUrl opens product selection on the External website tab, pre-fills and analyzes the URL even when no style asset resolves, and existing productId reuse links take precedence over external website prefill.

Conventions and Gotchas​

  • Do not assume creator role from client-only state. Use existing role/community hooks and server checks.
  • Use { data, error } for service APIs and show existing toasts for user-visible failures.
  • Keep admin/pro copy localized with direct t() calls.
  • Avoid broad abstractions across unrelated creator tools; many features have distinct service contracts.
  • Treat money/KYC/user data as sensitive. Do not add console output that exposes PII, tokens, or financial values.
  • For tables, forms, and dense admin screens, prefer quiet utility styling and predictable controls over decorative layouts.
  • .agents/rules/web-security.mdc
  • .agents/rules/no-try-catch-service-api.mdc
  • .agents/rules/clean-typescript.mdc
  • .agents/rules/clean-react.mdc
  • .agents/references/features/checkout-and-payments.md
  • .agents/references/features/onboarding-and-setup.md

Useful Searches​

rtk rg "Kyc|ProSubscription|NasPlan|revenue|LeadForms|Announcement|affiliate|coFounder|MagicContent|MagicAds|styleId|externalUrl" src/features src/hooks src/services src/pages
rtk rg "useUserRoleInCommunity|useCommunityRevenue|useNasPlan|moneyPageService" src
rtk find src/features/KycVerification -maxdepth 3 -type f

Update Triggers​

Update this reference when creator role checks, pro plan behavior, KYC status mapping, admin service contracts, revenue screens, or creator integrations change.