Settings & modules
How an institution's instance is configured: which modules appear, school type, branding text, login options and versioned application settings.
Each institution runs its own configured instance of Sivitas. Two layers control what users see.
Instance configuration (set at deployment)
A configuration file on the server, maintained by your IT team or by Sivitas, holds:
- Identity. University name and abbreviation, school or faculty name and abbreviation, help desk email, documentation link, login wallpaper.
- School type. Business switches on Assurance of Learning and FS/FQ/IC; other values hide them.
- Module switches. One flag per module: Program, Curriculum & Courses, Syllabus, Class & Teaching Assignment, AI scheduling, Teaching, People, FS/FQ/IC, HRD, DUPAK, Achievements, Assignment Letter, BAN-PT, RFID, Library, Final Project, Student Report, QA Survey, Setting, and per-category switches for achievement groups.
- Login options. Google Workspace, institutional SSO, email and password.
- Integration behaviour. Whether courses and classes are owned by Sivitas or synced from a source system, and which data-sync profile applies.
Changes here need a deployment step and apply to everyone. Ask your administrator or Sivitas support.
Application settings (in the app)
Sidebar › Setting lists key-value settings that can change without a deployment, each with its own Save. Settings are versioned by time period or order, so a value can differ per academic year (for example the credit value of a session or a document footer). The list is intentionally generic; the label describes each setting.
AI features
The AI parser, the scheduling assistant and the solver are configured by the administrator: the language-model driver and model, the API credential, and the solver's time and worker limits. See Deployment.
Checking what is enabled
Sign in with a Super Administrator account: the sidebar shows every enabled module. If a module you have licensed is missing, the flag is off in the instance configuration.