District IT & Security

PrincipalGO™ is a mobile-friendly Command Center for school leaders. It captures tasks and follow-ups by voice or text and organizes meetings, personal priorities, delegated work and items that need attention. The web application operates in desktop and mobile browsers at beta.principal-go.com during an invitation-based beta. Native iOS and Android apps are in development and are not required.

Recipients may respond to an assigned task through an expiring task-specific link without a PrincipalGO account. Email Sweep displays review cards; it does not send, delete, move or archive original messages during a sweep.

Authorize PrincipalGO as a third-party productivity application for eligible leaders to connect district-managed Google Workspace or Microsoft 365 accounts. District administrators control who may connect and can revoke provider-level access. If web filtering blocks the application, access to principal-go.com and beta.principal-go.com may also need to be allowed. Web access and OAuth or Entra authorization are separate controls.

Google Workspace OAuth

Microsoft 365 delegated permissions

Scope boundary: The product’s approved-location rules govern normal file workflows; they do not narrow the underlying Google Drive or Microsoft Graph permissions granted to the connected account. Review the provider consent screen and district policy before authorizing.

• Connected work account: Each leader signs into a private workspace and can have one active Google Workspace or Microsoft 365 provider at a time. Connecting does not by itself publish email, calendar events or files or change their sharing.
• Email Sweep: Selected sender, subject, snippet and message references may be stored in private review or task records. Original messages remain with Gmail or Outlook; PrincipalGO does not import the whole mailbox.
• Tasks and delegation: Task text, priorities, dates, assignments, status, contacts and history are stored. Principal-directed delegations go through the connected work mailbox. Response links have expiry and revocation checks.
• Calendars and documents: Source calendar entries remain with Google or Microsoft; source files remain in Drive or OneDrive. PrincipalGO may retain references and approved-location settings and create or modify files at the leader’s instruction.
• Photos and Brand Kit: Delegated photos travel as email attachments, without a permanent PrincipalGO photo library. A temporary on-device recovery copy can help an interrupted send. Brand Kit assets may remain in the workspace.

PrincipalGO does not directly connect to student-information or human-resources databases. District email and files may still contain confidential information. The district determines permitted information categories and workflows under its policies and agreements.

Google OAuth verification is complete. PrincipalGO passed its CASA AL1 security assessment on September 22, 2026. Google and Microsoft refresh credentials are encrypted with AES-256-GCM. Authenticated server endpoints protect connected operations, and users can disconnect work accounts.

Delegated-response links use token validation, expiry and revocation checks. A recipient’s link is limited to that assigned-task response, not the principal’s Command Center. District administrators retain their existing provider controls and may revoke the app’s access.

Vercel hosts the web application and API endpoints. Neon supports authentication and PostgreSQL workspace data; the current database is hosted in AWS us-west-2. Other infrastructure services, logs and backups may follow their providers’ arrangements.

Google Workspace or Microsoft 365 supports connected work functions. Resend delivers beta invitations and some automated task reminders, which may contain the recipient’s email address, task title, due date and response link. Principal-directed task delegations use the leader’s connected work mailbox.

Optional voice input uses the browser’s speech-recognition feature. Recognition may be processed by the browser provider depending on device and browser; leaders can type instead. Standard task, calendar and email workflows do not require a district to configure a separate generative-AI account.