Skip to content

What We Need From You

Scope: What we use to personalize CampusCore for your institution and make it ready for your users on day one. We apply all of this together during a short setup session.

Branding

These shape how the assistant and interface look and feel to your students and staff.

  • Institution name - the full name, for example "Howard University".
  • Institution abbreviation - the short form, for example "HU".
  • Assistant name - what people call the assistant, for example "Bison" or "Beacon".
  • Logo - your institution logo as an image file, uploaded in the setup wizard (optional).
  • Brand colors - your primary and secondary colors as hex values (optional). They style the sign-in page; the app itself keeps CampusCore's own colors on every deployment.
  • Login background photo - a campus photo for the sign-in page, at least 1920x1080 (optional; a default image is used otherwise).
  • Welcome message - a short greeting shown to users (optional; leave it blank and the assistant greets each user by name).

Your administrators

  • Initial administrators - who on your team should have administrator access to manage settings, branding, users, and knowledge. Tell us their university email addresses (the same identities they will sign in with through SSO).

Initial knowledge

CampusCore answers from the content you give it. You do not need everything on day one, but it helps to start with a core set.

  • Starter documents - handbooks, policies, FAQs, or guides you want available immediately (PDF, DOCX, and similar).
  • Content sources - the Google Drive folders, OneDrive folders, SharePoint libraries, and university websites you would like connected so their content is kept in sync. We handle the wiring.

Next: What Gets Configured.