Organization Settings are accessible to administrators (ORG_ADMIN role). Configure your institution's ScholarStack environment from Dashboard → Settings.
General Settings
- Organization name — the name displayed across the platform
- Timezone — the default institutional timezone used for due dates and scheduling
- Logo — upload your institution's logo for platform branding
AI Model Configuration
Go to Dashboard → AI Models to select which AI models power your ScholarStack instance. Choose from platform-provided models (Google Gemini, OpenAI GPT, Anthropic Claude) or connect your institution's own AI gateway for custom model access. Different models can be selected for different tasks (chat, grading, summaries).
Academic Calendar
Connect your institution's academic calendar under Dashboard → Integrations → Academic Calendar. This syncs term dates, holidays, and semester boundaries across all courses.
Data & Privacy
ScholarStack includes built-in tools for managing student data and generating compliance reports. All AI conversations are stored securely. Contact your Customer Success manager for detailed compliance and data retention configuration.
General Settings — What Each Option Does
- Organization Name — the name shown to students on the login page and in emails. Use your institution's official name (e.g., "University of Michigan — Engineering College").
- Logo — uploaded logo appears in the top navigation bar and on student-facing emails. Recommended: 400×100px, transparent PNG background.
- Primary Color — used for buttons, links, and accents throughout the platform. Must pass WCAG AA contrast ratio on white background.
- Timezone — the default timezone for displaying due dates and assignment times to professors. Students can override this with their personal preference.
- Academic Year Start — used to define the beginning of the current semester for analytics and reports.
Security Settings
- SSO (Single Sign-On) — connect your institution's identity provider (Google Workspace, Microsoft Azure AD, SAML 2.0). Once configured, all users log in through your institutional SSO and do not create separate passwords.