SharePoint site creation packet

Worker and creator true-site setup

Owner/admin packet for creating true SharePoint worker and creator sites without confusing them with the existing document-library portal folders.

Status: dry-run ready - true SharePoint sites still require owner/admin apply decision

Default mode is dry-run. No SharePoint site is created unless an owner/admin runs the guarded apply command.

32SharePoint Lists mapped
15worker-facing Lists mapped
2/2custom domains ready

Target sites

workers

ravefocus workers

Site: https://ravefocus.sharepoint.com/sites/ravefocus-workers

Future domain: https://workers.ravefocus.com

App link: https://agreeable-mushroom-05c98dd1e.7.azurestaticapps.net/workers

Status: not verified as created; latest connector check returned 404 before this packet was generated

creators

ravefocus creators

Site: https://ravefocus.sharepoint.com/sites/ravefocus-creators

Future domain: https://creators.ravefocus.com

App link: https://agreeable-mushroom-05c98dd1e.7.azurestaticapps.net/creators

Status: not verified as created; latest connector check returned 404 before this packet was generated

Creation targets

AreaPathTemplateAudienceOwner requirement
workers /sites/ravefocus-workers SITEPAGEPUBLISHING#0 or PnP CommunicationSite approved workers only tenant/sharepoint admin must choose the owner UPN at apply time
creators /sites/ravefocus-creators SITEPAGEPUBLISHING#0 or PnP CommunicationSite approved creators and owner-reviewed intake users tenant/sharepoint admin must choose the owner UPN at apply time

Libraries and permissions

AreaLibrary/page setPermission rule
workers worker onboarding workers get read/access only after Microsoft auth role assignment is tested; admin/owner retains full control; workers submit proof through role-safe forms/links and should not browse the proof vault
workers proof intake workers get read/access only after Microsoft auth role assignment is tested; admin/owner retains full control; workers submit proof through role-safe forms/links and should not browse the proof vault
workers quest evidence workers get read/access only after Microsoft auth role assignment is tested; admin/owner retains full control; workers submit proof through role-safe forms/links and should not browse the proof vault
workers public guides - read first workers get read/access only after Microsoft auth role assignment is tested; admin/owner retains full control; workers submit proof through role-safe forms/links and should not browse the proof vault
creators creator intake approved creators and support get only the sections they need; admin/owner retains full control; owner-only private records stay outside general creator pages
creators session proof approved creators and support get only the sections they need; admin/owner retains full control; owner-only private records stay outside general creator pages
creators public creator guides approved creators and support get only the sections they need; admin/owner retains full control; owner-only private records stay outside general creator pages

Go-live order

  1. Keep the verified workers.ravefocus.com and creators.ravefocus.com DNS records as-is; do not add duplicates.
  2. Use the saved domain DNS verification and finalization proof showing both custom domains are ready and both routes open.
  3. Create and verify SharePoint Lists/forms before switching worker forms out of draft-safe mode.
  4. Apply Microsoft auth and role/privacy rules before inviting workers or creators.
  5. Create true SharePoint worker/creator sites only if owner/admin decides they are needed beyond the current quest-center folders.
  6. Add site navigation links back to the Azure app, future custom domains, setup packet, forms, and safe guides.
  7. Run final live verification and preflight before worker launch.

Commands

Safety rules