Scholaris Cloud
HomeTroubleshooting
Scholaris Cloud — Platform Super Admin PlaybookFull platform operators who govern schools, support accounts, security policies, Resend email delivery, password resets, and platform-wide releases. · Entry Route: /admin

Platform Documentation & Execution Playbooks

Step-by-step execution playbooks for Super Admins, Platform Support, School Admins, Teachers, Parents, and Students.

8 workflows · 22 execution steps · /admin
Platform Super Admin PlaybookFull platform operators who govern schools, support accounts, security policies, Resend email delivery, password resets, and platform-wide releases.Access Scope: Global access across /admin and every tenant workspace.
0 / 22 steps completed (0%)
Execution Workflows
1. Navigate the Super Admin Console & Command Palette0/32. Provision, Inspect, Suspend, or Restore School Workspaces0/33. Send Email Invitations for Support Staff, Admins, or Schools0/34. Diagnose Resend Email Delivery & Inbound Inbox Routing0/35. Create Support or User Accounts Directly (No Wait for Invite)0/36. Reset User Passwords (Email Link or Temporary Password) & Force Sign-Out0/37. Manage Cross-School Memberships & QA Sandbox Tools0/28. Publish Platform Release Notes ("What’s New")0/2
Troubleshooting & FAQ

1. Navigate the Super Admin Console & Command Palette

Orient yourself across the 7 platform administration views and jump instantly to any school, user, or action with keyboard shortcuts. · Est. 3 min
0 / 3 done
01
Open the Super Admin Console
Sign in with a verified Platform Super Admin account and navigate to /admin. The left sidebar displays Overview, Schools, Platform Users, Platform Audit, Releases, Operations, and Documentation.
Expected Result: The Overview screen displays live platform KPIs (Total Schools, Active Users, Pending Invites, Recent Activity) and quick health signals.
02
Use Quick Search (Cmd/Ctrl + K)
Press Cmd+K (macOS) or Ctrl+K (Windows/Linux) or click the search trigger in the top bar. Type a school name, slug, or view name (such as "users" or "releases").
Expected Result: Matching schools and navigation actions appear immediately; press Enter or click to jump straight to that screen.
03
Review your active operator status
Confirm the top header displays "Super Admin" access rather than "Platform Support". Super Admin unlocks user creation, role promotions, temporary passwords, and Resend diagnostics.
Expected Result: All privileged actions (Invite to Platform, Create Account, Email Diagnostics, and School Provisioning) are active and enabled.

2. Provision, Inspect, Suspend, or Restore School Workspaces

Create new school tenants from the console, inspect their live stats, or suspend/restore access during billing or compliance reviews. · Est. 5 min
0 / 3 done
01
Open the Schools Registry
Click "Schools" in the left navigation rail to open the master directory of every tenant workspace on Scholaris Cloud.
Expected Result: A searchable table lists each school name, URL slug, status (Active/Suspended), student/staff counts, and quick inspection actions.
02
Inspect a school workspace before making changes
Click "Inspect" on any school row to open the School Inspector drawer. Review its active members, campuses, academic years, and recent audit entries.
Expected Result: You can view the tenant health snapshot without leaving /admin, and you can jump into its live workspace via audited impersonation if needed.
03
Suspend or restore a school safely
From the Schools table or School Inspector, use the Suspend action (with a clear reason) to freeze tenant logins, or Restore to re-enable access immediately.
Expected Result: The tenant status updates in PostgreSQL immediately and writes an immutable entry to Platform Audit with your actor ID and timestamp.
Operator Tip: Never delete production schools directly; suspend first so school admins can export records or resolve billing before archival.

3. Send Email Invitations for Support Staff, Admins, or Schools

Onboard new Platform Support agents, additional Super Admins, school members, or new school owners via Resend-delivered single-use links. · Est. 4 min
0 / 3 done
Prerequisites: RESEND_API_KEY configured in server secrets and scholaris.cloud verified for sending in Resend.
01
Open Platform Users and click Invite to Platform
Navigate to Platform Users in the sidebar and click the "Invite to Platform" button in the top-right action bar.
Expected Result: The Invite to Platform dialog opens with fields for Invitee Email, Full Name, Invitation Scope, Target School (if school_member), Personal Note, and Expiration Window.
02
Choose the exact invitation scope
Select one of four scopes: Platform Support Agent (scoped /admin access), Platform Super Admin (full control), School Member (assign directly to an existing school + role), or New School Owner (redirects to /onboarding).
Expected Result: The form adapts automatically—requiring School and School Role only when "School Member" is selected.
03
Submit and verify delivery + copyable fallback link
Click "Send Invitation". Review the confirmation banner showing whether Resend accepted the message ("Email Sent") and copy the one-time /invite/platform/... URL as a backup if needed.
Expected Result: A new pending row appears in the Platform Invitations table showing recipient email, scope, expiration date, and Resend status. The recipient must sign in or register using that exact verified email address.
Operator Tip: Use Resend or Revoke buttons on any pending invitation row to rotate a lost link or cancel an unused invite immediately.

4. Diagnose Resend Email Delivery & Inbound Inbox Routing

Verify live Resend domain DNS records, inspect real delivery events (delivered vs. bounced), and troubleshoot why emails sent to support@scholaris.cloud may not appear in Resend Inboxes. · Est. 5 min
0 / 3 done
01
Open Email Diagnostics from Platform Users
Go to Platform Users and click "Email Diagnostics" in the page header or inside the Platform Invitations card.
Expected Result: The Resend Email Diagnostics dialog loads active sender configuration (From: admin@scholaris.cloud, Reply-To: support@scholaris.cloud), domain verification status, and recent sent emails.
02
Check Sending vs. Receiving (Inbound MX) status on scholaris.cloud
Inspect the Domains table inside Email Diagnostics. Confirm both Sending (SPF/DKIM) and Receiving (Inbound MX) show Verified. Remember that "Email Sent" in the invitations table means Resend accepted the API request—not that an inbox received it.
Expected Result: If Inbound Receiving is disabled or missing its MX record on scholaris.cloud, a warning callout highlights the exact DNS step required in Resend Dashboard -> Domains -> scholaris.cloud.
Operator Tip: Sending SPF/DKIM records only authorize outbound mail. Receiving mail at support@scholaris.cloud inside Resend Inboxes requires toggling Receiving ON and adding Resend’s Inbound MX record at your DNS host.
03
Run a live Send Test Email check
Enter an external address you control (for example a Gmail or Outlook address) into "Send Test Email", click Send Test, wait 5 seconds, then click "Refresh Status".
Expected Result: The Recent Sent Emails table displays the new Resend Message ID and live Resend event (delivered, queued, delivery_delayed, or bounced). Confirming external delivery proves outbound sending works independently of scholaris.cloud inbound MX routing.

5. Create Support or User Accounts Directly (No Wait for Invite)

Provision an active Neon Auth login and Scholaris profile immediately with a generated temporary password and optional school membership. · Est. 4 min
0 / 3 done
01
Launch Create Account
In Platform Users, click "Create Account". Enter the user’s full name, email address, and choose their Platform Role (Standard User, Platform Support, or Platform Super Admin).
Expected Result: The dialog prepares both the Neon Auth credential and the Scholaris database profile.
02
Optionally attach an initial school membership
Select a target school and school role if the user should immediately land inside a school workspace upon login.
Expected Result: The membership and role assignment are saved atomically alongside the new user profile.
03
Copy the one-time temporary password
Submit the form. Copy the generated temporary password displayed in the confirmation dialog and deliver it to the user over a secure channel.
Expected Result: The user can sign in right away at /login and immediately change their password.
Operator Tip: Temporary passwords are shown once at creation time and are never stored in plaintext in Scholaris.

6. Reset User Passwords (Email Link or Temporary Password) & Force Sign-Out

Help locked-out users recover access or immediately lock down a compromised account by revoking all active sessions. · Est. 3 min
0 / 3 done
01
Locate the user in Platform Users
Open Platform Users and search by name or email, or filter by Platform Role (All, Super Admin, Support, Standard) and Status (Active, Suspended).
Expected Result: Clicking the user row opens their Governance Drawer with Profile, Memberships, Security Actions, and Per-User Audit tabs.
02
Choose Reset Email vs. Set Temporary Password
Click "Reset Password". Select "Send Reset Email" to trigger Neon Auth’s official password reset link, OR select "Set Temporary Password" (Super Admin only) to assign a fresh password immediately and invalidate old sessions.
Expected Result: The user receives a reset email or you receive a one-time copyable temporary password. The action is permanently recorded in audit_logs.
03
Force Sign-Out or Suspend compromised accounts
Inside the user’s Governance Drawer, click "Force Sign-Out" to revoke every active Neon Auth session token immediately. Toggle account Status to Suspended if the user should be blocked from logging back in.
Expected Result: All active sessions for that user are terminated server-side and recorded in the user’s Audit History tab.

7. Manage Cross-School Memberships & QA Sandbox Tools

Assign or remove school roles for any user across multiple schools, and use Operations for safe sandbox seeding and impersonation audits. · Est. 4 min
0 / 2 done
01
Edit a user’s school memberships
Open any user’s Governance Drawer in Platform Users and go to the Memberships section. Add a school + role (Owner, Admin, Teacher, Staff, Student, Parent), update an existing role, or remove membership access.
Expected Result: Row-level security (RLS) immediately reflects the updated membership on the user’s next request.
02
Run Operations checks and QA sandbox workspaces
Open the "Operations" view in the Super Admin sidebar to review platform diagnostics, database health, and sandbox provisioning tools.
Expected Result: You can verify platform readiness and test school workflows in an isolated sandbox without touching live customer schools.

8. Publish Platform Release Notes ("What’s New")

Announce new features, maintenance notices, and workflow improvements directly inside every signed-in user’s sidebar. · Est. 3 min
0 / 2 done
01
Open Releases in the Super Admin Console
Click "Releases" in the left navigation rail to manage platform-wide changelog entries and feature announcements.
Expected Result: Existing published and draft release announcements are displayed chronologically.
02
Draft, publish, and verify in-app visibility
Create a concise title, select the target audience, write clear bullet points of what changed, and publish. Click "What’s New" in the bottom-left sidebar to verify how users see the announcement.
Expected Result: Signed-in admins and staff see an unread badge on What’s New and can read your release update immediately.

Super Admin Troubleshooting & Common Questions

Verified causes and step-by-step fixes for common operational issues.
Platform invitation says "Email Sent", but nothing arrives in support@scholaris.cloud.Why it happens: Resend returns 200 OK ("Email Sent") as soon as the send request is queued. Receiving email at support@scholaris.cloud inside Resend Inboxes requires Inbound Receiving to be enabled on scholaris.cloud with a verified Inbound MX DNS record (separate from SPF/DKIM sending records).How to fix: Open Platform Users -> Email Diagnostics. First send a test email to an external address (e.g. Gmail) to confirm outbound sending works. Then open Resend Dashboard -> Domains -> scholaris.cloud, toggle Receiving ON, add the Inbound MX DNS record at your registrar, and click Refresh Status in Email Diagnostics.
Email Diagnostics says the API key cannot read domains or delivery events.Why it happens: The configured RESEND_API_KEY was created with "Sending access" only, so Resend returns 401/403 on GET /domains and GET /emails/{id}.How to fix: Sending invites still works with a sending-only key. To unlock live MX checks and delivered/bounced telemetry inside Scholaris, generate a Full Access API key in Resend and update RESEND_API_KEY in your environment secrets.
Invited user sees "Email mismatch" or "Verify your email" on /invite/platform/...Why it happens: Scholaris enforces a strict security invariant: invitation acceptance requires a verified email address matching the exact email the invitation was issued to.How to fix: Confirm the user registered and verified the exact email shown on the invitation card (case-insensitive). If they used a different email, revoke the old invite and send a fresh invite to their verified address.