Key ideas in one page #
TihTur is built from a small number of building blocks. Once you know them, every screen makes sense. Read this page before you set anything up.
The building blocks #
| Idea | What it is | School example |
|---|---|---|
| Entity (structure) | One school or branch. Every task belongs to one entity. | Nihoc International School, Nihoc International Begumpet |
| User | A person who signs in. | The Principal, a class teacher, a parent |
| User type | The kind of account. It decides the menus a person sees. | Job for staff, Default for parents and students, Admin for the office that runs the system |
| Role | What a person does, and therefore what they may see and approve. A user can hold many roles. | Principal, Class Teacher, Accountant |
| Document group | A folder of related document types, of one of three kinds: Apply, Create or Index. | Admissions (Apply), Staff HR Requests (Create), Finance Records (Index) |
| Document type | One kind of request or record. | Admission 2027-28, Staff Leave Request, Fee Receipt |
| Form | The questions of a document type, in groups. | Student information, parents, documents to upload |
| Tags | Extra details recorded while processing a request, or the key details of a filed record. | Admission Number, Section Allotted, Fee Amount |
| Workflow | The steps a document goes through, and the actions that move it between steps. | Received → Verification → Assessment → Principal → Admitted |
| Task | One submitted request or filed record, moving through its workflow. | Aarav's admission application |
| Data table | A master list the forms read from. | Classes, bus routes, fee schedule, students, staff |
| Dashboard | A live view over tasks and their tags. | Admissions this month, by class and status |
| Report | A statement for a period, with totals and comparisons. | Fee Collection Statement |
| Profile type | A bundle of extra permissions, such as attachments, dashboards or deleting tasks. | Power User |
The three kinds of document #
| Kind | Who uses it | What it is for | Examples |
|---|---|---|---|
| Apply | Parents, students, job applicants | Asking the school for something | Admission, transport, hostel, scholarship |
| Create | Staff | Internal requests and approvals | Leave, purchase, lesson plan, incident report |
| Index | Office, accounts, records staff | Filing a document with its key details | Fee receipt, vendor invoice, licence, audit report |
The kinds of role #
| Role type | What it gives | Naming used in the demo |
|---|---|---|
| Job role | A position in the school. Used as the approver of workflow steps. | NIHOC_Principal_JR, NIHOC_ClassTeacher_JR |
| Approval role | The right to approve one kind of decision, independent of the job. | NIHOC_StaffLeaveApproval_AR, NIHOC_AdmissionApproval_AR |
| Security role | Access to a family of documents, for searching and viewing. | NIHOC_FinanceRecords_SR, NIHOC_StudentRecords_SR |
| Property role | Membership of one school or branch. | NIHOC_PR (main campus), NIHOCBP_PR (Begumpet) |
Green card (AdminRole) |
Sees and can act on every document type. | The system administrator |
| Orange card | Sees every document type, dashboard and report, but cannot change anything. | The public demo login only |
How they fit together #
- A parent (user type Default, holding the Parent job role and the school's property role) submits the Admission form.
- That creates a task in the school's entity, at the first step of the Admission workflow.
- The step's approver role (Admissions Officer) decides who is asked to act. Only Admissions Officers of that school are asked.
- Each action (for example Documents Verified) moves the task to the next step and is written to its history.
- Staff record tags on the way (test score, section, admission number).
- Dashboards and reports read the tasks and their tags, so management sees the admissions pipeline without anyone preparing it.
Ready to set up? Continue with the Setup plan and checklist.