Roseville Joint Union High School District
RJUHSD Administrator app hub
Ed Services and Technology Services
September 2026

Administrator app hub

One front door for everything your team builds.

A home for every tool, a review before it goes live, one place to find it.

Proposal · for discussion · nothing deployed yet

The ask Keep the hub you have. Add a Drive folder for ChatGPT builders. Let Comms curate the rest.

Where things stand.

LiveThe apps repoFifteen apps at rjuhsd.app
LiveThe gated hubDistrict sign-in, cabinet owners
GapNo way in from ChatGPTA file with nowhere to go
GapBuilt elsewhere, listed nowhereTools with no card on the hub

Two doors in. One hub out.

DOOR A · MOST STAFF Build in ChatGPT Enterprise workspace Drop it in Drive Hub Submissions folder DOOR B · POWER BUILDERS Build with Claude Code As today Push to the repo Unchanged REVIEW Checked, then approved LIVE rjuhsd .app On the hub

ReadData stays in the builder's Google. The repo holds code only.

The reviewer watches. A person decides.

Returned with a note. The builder re-drops the file. 1 · WATCH Reads the folder Every hour 2 · CHECK Runs the checks Secrets, outside calls, student data 3 · REPORT Comments on the file Right in Drive 4 · DECIDE Ed Services replies "approve" or "return" 5 · PUBLISH Live on rjuhsd.app Builder gets the link approve return

ReadThe reviewer never publishes on its own. Student data always waits for a person.

Approve or return, from a Drive comment.

Approve
site-supply-requests.html
Hub Reviewer7:05 AM

Staff-only request form. One Sheet in the builder's Drive. No student data.

No secretsDistrict Google onlyNo student data

Reply approve or return.

Ed Services7:40 AM

approve

Hub Reviewer7:41 AM

Live at rjuhsd.app/supply-requests. Builder notified.

Return
counselor-caseload-view.html
Hub Reviewer7:05 AM

Lists students by name. Student data, so I will not publish this on my own.

Student dataNo secrets

Ed Services8:10 AM

return. Needs per-counselor sign-in first.

Hub Reviewer8:11 AM

Returned with your note. Builder notified.

The log
FileChecksDecisionByResult
site-supply-requests.htmlpassapproveEd Serviceslive
counselor-caseload-view.htmlflagreturnEd Servicesreturned
bell-schedule-board.htmlpasspendingwaiting
next file

One row per submission. Every decision on record.

Four people. Four jobs.

01 Builder

Drop a file.

Build it in ChatGPT. Download. Drop it in Hub Submissions.

02 Ed Services

Reply approve.

The facts arrive with the file. Student data always waits for you.

03 Comms

Edit one sheet.

Links, pilot updates, guidance. The hub reads it.

04 Reviewer

Check everything.

No secrets. No outside calls. No student names in the page.

What the hub becomes.

RJUHSD APPS Admins and directors · district sign-in
Dashboards
Site WalkthroughsInstructional Leadership
ATLAS Protocol LogInstructional Leadership
IEP FeedbackSpecial Education
SLD EvaluationsSpecial Education
Tools
Admin WalkthroughEd Services
Check-InEd Services
SpEd AssistantSpecial Education
Cohort builds land hereafter review
Resources and updates
ChatGPT Enterprise pilotwho is in, how to join
AI guidance for staffpolicy and parameters
Curated by Commslinks, files, updates

What changes. What stays.

WhereWhat lives there
Builder's GoogleThe data. Never copied out.
Submissions folderDistrict Drive, owned by Ed Services.
Apps repoCode only. Yours whenever you want it.
rjuhsd.appHosting. Rollback is one revert.

ChangesCohort members can publish. Comms has a hub to curate.

StaysAmy and Josh build and push exactly as today.

Needs ITOne service account on the submissions folder.

Decisions for this meeting

  1. Is the hub the front door, with Comms curating Resources?
  2. Who approves, and what can go live without waiting?
  3. Who is in the ChatGPT Enterprise pilot?
  4. Does the cohort learn the Drive door next session?

AI flyers and promotional items are a policy call. The hub gives that guidance a home once it exists.