SharePoint + ravefocus.com routing

Worker and creator site-area plan

Clarify how the worker and creator portal areas should connect to SharePoint and ravefocus.com without confusing current SharePoint folders with true SharePoint sites.

Status: site-area decision ready after SharePoint/auth setup review

Azure Static Web App is the running portal; SharePoint quest-center folders are launch archive, handoff, storage, and future site/page setup areas.

2/2custom domains ready

15worker-facing Lists mapped

4access roles mapped

Current SharePoint areas

workers

current SharePoint document-library folder

Worker docs, launch proof, and forms/list handoff notes while the Azure app remains the running portal.

Status: exists as portal handoff/storage folder; not a separate SharePoint site

https://ravefocus.sharepoint.com/Shared%20Documents/website%20-%20quest%20center/worker%20portal%20-%20workers

creators

current SharePoint document-library folder

Creator docs, launch proof, intake handoff notes, and creator-safe onboarding context.

Status: exists as portal handoff/storage folder; not a separate SharePoint site

https://ravefocus.sharepoint.com/Shared%20Documents/website%20-%20quest%20center/creator%20portal%20-%20creators

admin

current SharePoint quest-center folder

Launch archive, setup packet, proof reports, dashboard handoff, and private admin setup evidence.

Status: active launch archive and fallback package location

https://ravefocus.sharepoint.com/Shared%20Documents/website%20-%20quest%20center

Recommended site split

area	SharePoint site path	public route	audience	permission gate
workers	`https://ravefocus.sharepoint.com/sites/ravefocus-workers`	`https://workers.ravefocus.com`	approved workers only	Microsoft auth and worker role assignment required before invite traffic
creators	`https://ravefocus.sharepoint.com/sites/ravefocus-creators`	`https://creators.ravefocus.com`	approved creators and owner-reviewed intake users	Microsoft auth/privacy rules required before private creator data is connected
admin	`https://ravefocus.sharepoint.com`	`none`	owner/admin only	owner/admin role required

Launch options

recommended

keep Azure app as the running portal and use SharePoint sites/folders as the work-data hub

Keeps the fun game HUD fast and branded, while SharePoint stores controlled Lists, forms, documents, proof folders, and admin evidence.

Launch impact: lowest risk; keep verified custom domains as-is, then finish SharePoint Lists/forms, auth, and links first

possible later

create true SharePoint worker and creator sites

Useful if workers/creators should land inside SharePoint navigation first, with the Azure app embedded or linked from there.

Launch impact: requires owner/admin site creation, navigation, permissions, page publishing, and link retesting

not recommended for launch

move the full game HUD to SharePoint native pages only

SharePoint pages are strong for docs and lists, but weaker for the custom HUD/game interface and fast UI iteration.

Launch impact: higher rebuild effort and more design limitations

Launch gates

gate	status	proof
GoDaddy DNS	custom domains verified	`outputs/domain-dns-verification-report.html`
SharePoint Lists/forms	mapped; live creation still gated by Microsoft permissions	`outputs/sharepoint-go-live-checklist.html`
auth/privacy	mapped; not enforced	`outputs/auth-owner-action-sheet.html`
worker/creator SharePoint site creation	owner/admin decision required before creating true sites	`outputs/sharepoint-worker-creator-site-create-packet.html`

Owner actions

Keep the Azure Static Web App as the running worker/creator portal for launch unless you explicitly want true SharePoint sites created first.
Keep the verified workers.ravefocus.com and creators.ravefocus.com DNS records as-is; do not add duplicates.
Decide whether true SharePoint sites should be created as /sites/ravefocus-workers and /sites/ravefocus-creators, or whether the current document-library folders are enough for launch.
If true SharePoint sites are needed, use outputs/sharepoint-worker-creator-site-create-packet.html before running the guarded site creation helper.
Create SharePoint Lists/forms before switching worker forms out of draft-safe mode.
Apply Microsoft auth and role rules before inviting workers or exposing private creator/work records.
Use only proof-safe links in worker/creator pages. For sensitive proof, write owner-only private record required.

Safety boundary

Do not add passwords, recovery codes, billing/card/bank info, payout settings, ID photos, private fan/customer records, private creator records, or platform recovery details to worker/creator pages.
Workers should not need access to the proof vault. They submit proof through role-safe forms/links, then admin reviews it privately.
No proof = no payout. No assigned quest = not payable. No approved task order or written approval = not payable.
If sensitive proof is needed, write owner-only private record required.