CampusCore Onboarding¶
Admin Account Setup¶
One-time setup of the CampusCore admin AWS account (OIDC role, S3 permissions, Route53). Already completed — only needed if migrating to a new admin account.
Client Onboarding¶
Step-by-step guide for deploying CampusCore to a new university. Start here for each new client.
The front door is scripts/onboard-client.sh (or /onboard_client in Claude Code): an interactive, resumable journey that runs the automatable steps and hands you the rest.
Reference¶
| Doc | Description |
|---|---|
| GitHub Environment Variables | Complete list of all secrets and variables per environment |
| Repo & Pipeline Setup | How repo-level GitHub secrets/variables were configured |
| Sentry Setup | Create the Sentry project, set GitHub Environment secrets/variables, install Slack + GitHub integrations, end-to-end verification |
| Slack Setup | Install the Slack app, point each environment at the shared client_workflow_runs channel, troubleshoot the variable-vs-secret namespace gotcha |
| Google Connectors Setup | Create the Google OAuth app for the Gmail, Google Calendar, and Google Drive connectors |
| Microsoft Connectors Setup | Register the Entra app shared by the Outlook Mail, Outlook Calendar, OneDrive, and SharePoint connectors |
| ServiceNow Setup | Register the OAuth Application Registry entry and configure the CampusCore ServiceNow connector |
| Configuring SSO Roles | Map an institution's IdP groups to CampusCore roles so users get the right access on every login |
| Managing Features | How institution admins enable, disable, and role-scope features in the in-app Features settings |