planner 3 portfolio setup for ravefocus worker hub

current working layer

The live worker quest hub is already connected to this Planner plan:

Group: RaveFocus Worker Quest Hub
Group ID: e1ec0692-7ef2-4954-8bae-01e33fdb0887
Plan: ravefocus worker quest hub
Plan ID: NdzIARGlwkmiwuNuvcwRWmUACvnz

This plan was created through Microsoft Graph as the worker-facing dispatch board. It is useful for exact task IDs, bucket IDs, task links, assignments, proof links, and website compatibility.

Browser setup index:

outputs/planner-premium-setup-index.html

planner 3 portfolio layer

Create a Planner 3 portfolio named:

ravefocus worker portfolio

Use it as the admin/owner view across premium plans. The portfolio should not replace the existing worker dispatch board; it should sit above it.

Recommended premium plans to add to the portfolio:

ravefocus worker quest hub - premium mirror of daily dispatch and assigned worker tasks
content scheduling + approvals - calendar, content approvals, campaigns, and platform queues
lenslab editing pipeline - edit requests, raw assets, revisions, final exports, and handoffs
lineup bookings + pop-ups - bookings, venues, call times, run of show, shoot proof, and pop-up completion
echo chatter + safe crm - shift summaries, safe CRM notes, fan follow-up routing, and escalation
signal analytics + reports - metrics, winners, performance logs, and report requests
jupiter approval + restricted review - owner approvals, compliance uncertainty, money/contracts/legal, blocked work, and payout review

premium fields to create

Use these as the recommended custom-field pool. Planner Premium custom fields are plan-specific, so choose the most relevant fields for each premium plan and keep each premium plan to its available custom-field limit.

role seat
client / creator
event or shoot name
booking type
date needed
location
crew needed
sharepoint folder
proof link
calendar updated
approval status
jupiter review
blocked reason
final handoff link
sensitivity level

Choice values:

calendar updated: no, yes, needs correction, not needed
approval status: not submitted, submitted, needs correction, approved, rejected, completed, archived
sensitivity level: public, internal, restricted, jupiter only, compliance restricted

important limitation

Microsoft Planner portfolios are for premium plans. The current Graph-created worker plan remains the website-compatible dispatch board. Create a premium mirror plan for portfolio reporting, then connect it to the portfolio.

Planner Premium custom fields are plan-specific. Do not try to force every recommended field into every premium plan. Use role-specific sets:

Lineup: role seat, event or shoot name, booking type, date needed, location, crew needed, sharepoint folder, proof link, calendar updated, approval status
LensLab: role seat, client / creator, date needed, sharepoint folder, proof link, approval status, jupiter review, blocked reason, final handoff link, sensitivity level
Echo: role seat, client / creator, proof link, approval status, jupiter review, blocked reason, sensitivity level
Signal: role seat, date needed, sharepoint folder, proof link, approval status, blocked reason, final handoff link, sensitivity level
Jupiter/restricted: role seat, proof link, approval status, jupiter review, blocked reason, final handoff link, sensitivity level

Do not paste private customer/fan info, payout settings, billing, card, bank, passwords, recovery details, ID photos, legal/compliance records, or owner-only records into Planner. Use owner-only private record required when sensitive proof exists elsewhere.

workflow connection

Use SharePoint Lists as the live form record layer:

task requests create or update Planner tasks
proof submissions update task proof status
approval requests route to Jupiter/admin
content scheduling updates calendar and approval state
shift submissions feed Echo/admin review without exposing private fan records

For payout eligibility:

no proof = no payout
no assigned task = not payable
no approved task order or written approval = not payable