The Terminology Configuration page allows you to replace the default terms used throughout InstiKit with terminology that is more familiar to your organization.
Different schools, colleges, universities, and institutions often use different names for the same concept. Instead of forcing everyone to use a single terminology, InstiKit allows you to customize labels without modifying the application.
For example:
- Course → Class
- Batch → Section
- Guardian → Parent
- Employee → Staff Member
These changes are reflected automatically throughout the application.
Important
Terminology changes affect only the labels displayed in the user interface.
They do not modify your existing data or database structure.
Global Terminology
Global terminology allows you to rename commonly used terms throughout the entire application.
Once a term is changed, every screen that uses that terminology will automatically display the new label.
Example
If you change:
Course → Class
then throughout InstiKit you will see:
- Add Course → Add Class
- Course List → Class List
- Course Details → Class Details
- Select Course → Select Class
Similarly,
Batch → Section
will automatically change labels such as:
- Batch List → Section List
- Batch Details → Section Details
This makes the application feel more natural for your organization.
Context-Specific Labels
Sometimes you only want to rename a label in a specific screen instead of changing it everywhere.
For these situations, InstiKit provides Context-Specific Labels.
A context-specific label overrides the translation only for a particular page, component, or module.
Unlike global terminology, it does not affect other parts of the application.
Example
Suppose the Student Admission module contains the label:
Admission Number
Internally, it may be identified as:
student.admission.props.code_number
If your organization prefers the term:
Enrollment Number
simply enter:
Translation Key
student.admission.props.code_number
Value
Enrollment Number
Only that particular label will change.
Other labels using the word Number or Admission elsewhere in the application remain unchanged.
When to Use Global Terminology
Use Global Terminology when the same word should change everywhere.
Examples include:
- Course → Class
- Batch → Section
- Guardian → Parent
- Employee → Staff
When to Use Context-Specific Labels
Use Context-Specific Labels when only one screen or module requires a different label.
Examples include:
- Admission Number → Enrollment Number
- Roll Number → Student ID
- Leave Reason → Reason for Absence
- Title → Subject (only in one module)
This allows very precise customization without affecting the rest of the application.
Best Practices
- Change terminology only when necessary.
- Use terminology that is familiar to your staff.
- Keep naming consistent across your organization.
- Prefer Global Terminology when the same label should change everywhere.
- Use Context-Specific Labels only for special cases.
Important Notes
- Terminology changes affect the user interface only.
- Existing records and database fields are not modified.
- Changes take effect immediately after saving.
- Future InstiKit updates may introduce additional terminology that can also be customized.
Saving Changes
After updating terminology, click Save to apply the changes.
Users may need to refresh their browser before updated labels become visible throughout the application.