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.
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, create the per-client workflow_runs channel, invite the bot, capture the channel ID, troubleshoot the variable-vs-secret namespace gotcha |
| Google Drive Setup | Enable Google Drive integration for a university |
| 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 |